Ya, PEQ runs on Linux. And my linux box maybe gets 100-250mbs of log files per day or so, but I restart it every day or 2 anyway and the startup scripts erase all of the log files and start new ones. Linux handles the logs MUCH better than windows does for sure.
One thing I would love to see would be trying to disable almost all debugs accept for the most important ones in the source and seeing how much performance is gained. I bet it would be a surprising amount even on Linux. I know this isn't exactly related, but when I worked at AT&T, we weren't allowed to turn debugging on for the routers ever. This is because the huge amount of traffic that the backbone took would cause enough of a performance hit if you enabled certain debugs that it would crash the router for sure due to the processors not being able to handle that much more work load. But as long as you left debugs off, their processor utilization was at about 1%. I know debugging every packet is MUCH more work than all of the debugs that eqemu does, but I am also sure that debugs can and do use a considerable amount of resources.
I would LOVE to see some easy way to turn debugs on and off with a command, rule, or setting somewhere. Then you could use them when you want, and disable them when you have no need for them. The only way I know to keep the debugs from being processed at all is to remove each one from the source line by line (or comment out) and then recompile. That isn't exactly an "easy" way to turn them on or off tho lol.
Even by changing the log directory name, I think the debugs are all still processed, they just don't get written to the file, which that alone is enough to probably help performance some. But if they were disabled completely, I think it would make a considerable difference.
Maybe I will experiment with them sometime if I ever get the time to go through and comment them all out and recompile lol.
|
Threaded Mode
