Well, using threads carefully is what rsyslog alre...

2010-02-12T17:57:55.859+01:00

Well, using threads carefully is what rsyslog already does. I am also not sure if nginx attitude towards syslog logging is correct. This independent blog post claims to do 250,000 msgs per second with rsyslog:

http://mperedim.wordpress.com/2010/01/21/rsyslog-evaluation/

My personal testing, on non-high end hardware tells me about 110,000+ messages per second.

There is a huge difference between the simple model of legacy syslogd and what rsyslog does.

See Nginx for an example of a VERY high performanc...

2010-02-12T16:53:23.733+01:00

See Nginx for an example of a VERY high performance tcp server which uses only moderate amounts of threading in order to handle very high loads across multiple cores.

You need to be careful that introducing more threads may or may not improve speed on a typical system... In fact because threads consume resources it's frequently faster to use fewer threads rather than more threads in a given scenario?

I believe nginx doesn't multithread accepting tcp connections for example, but it does obviously multithread processing them.

Remember also that nginx is an example of a VERY high throughput server which for example rejects syslog logging as being too slow to keep up!

Just a thought to investigate before putting to much development working into parallelising, that it's going into the correct place?

Comments on Rainer's Blog: rsyslog multithreading

Well, using threads carefully is what rsyslog alre...

See Nginx for an example of a VERY high performanc...