Okay, i guess you all wanna hear success stories?
Well i got one for ya!
Before:
Using syslog/splogger.
50 in concurrencyremote.
I do a "killall -ALRM qmail-send".
Syslog was at >80%, mostly kernel time.
Not counting qmail daemons CPU%.
Load was at worst ~3.50.
The box was kinda crawling (that means you can't play quake on it :) ).
After:
Using multilogger.
110 in concurrencyremote.
I do a "killall -ALRM qmail-send".
Syslog was quiet (well it should be :)
WHOLE SYSTEM cpu usage was around 6-8% (with ~100 qmail-remote's doing their
thing, but they were mostly rejected by different (but leagal) reasons)
The load was at worst ~0.80.
I could play quake quite nicely.
Salute to multilogger over syslogd for this kinda biz!
/Magnus N�slund
