Open MiguelMonge opened 10 years ago
Hi,
wow, 2 000 devices is A LOT and a big challenge for Octopussy... (and I understand now why you want to reduce octo_(u)parser(s) memory usage ! :) )
One solution to reduce inodes usage would be to have one file by device/service/X minutes/hours instead of current device/service/minute.
But here again, it's a lot of code rewriting... :(
Regards, Sebastien
actually, I have a similar issue, but also a long term storage issue.
I was thinking that it is easy to concatenate gzips and gradually change the granularity, the log rotation process could do this as well as delete old logs. I'm aware that the readers need to change a lot, but this would avoid changing the writers.
Would this be a change you would consider?
HI: now i'm using a XFS file system (you can use ReiserFS to) and this what the system works fine.
i added an additional disk.
Hi! i have 486 devices and i project to add 1600 devices more or less, because the system make a lot of files my inodes file sistem are full.
My server is virtual and have a 25 GB of hard drive, i going to add a other virtual disk of 100 GB with ReiserFS because this have a inodes white dynamic assignation.