On Thu, 5 Nov 2015, Otis Gospodnetić wrote:
Hi,
JB: nice retro monitoring! :)
Would seeing the output of dstat help? I wonder if there is a pile of
context switching. We'll see what CPU wait looks like and what disk
read/write utilization is like.
To me this sounds like some bug that simply doesn't dedicate enough threads
(or something along those lines) to reading from disk or gives it such low
priority that it just doesn't pick up enough data from disk relative to how
much it prefers sending logs from memory.
rsyslog does prefer to send logs from memory.
my guess is locking and too many small I/O ops (especially too many syscalls)
that end up getting serialized behind each other.
David Lang
_______________________________________________
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.
