It was thus said that the Great Justin Lee once stated: > > Since Linux allow more than one processes have the same priority, > rsyslogd could still be preempted by other processes with the same > priority even if the given priority is the highest one, as in 'Kernel > preemption on same priority tasks' > <http://stackoverflow.com/questions/17831970/kernel-preemption-on-same-priority-tasks>: > "in general case, if your processes have equal priorities, process > with less run-time will preempt another process on the next schedule() > invokation." > > In addition, if the latency due to scheduling could be resolved by > configuring priority, the two projects D-Bus & Wayland should have > adopted it and no need to move code to the kernel or offload from > server to client processes. So in conclusion, giving rsyslogd high > priority doesn't resolve the issue.
There are still things you can do if it's very important. 1. Measure to see if this is even an issue. 2. On a multicore system, you can pin rsyslogd to a single core, and prevent other processes from running on that core. Taken to an extreme, dedicate one core to rsyslogd, one core to handling interrupts (or dedicate it to the kernel), leaving the rest for other processes. 3. Dedicate one computer (or several) to rsyslogd. -spc _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
