On Thu, 19 Sep 2013, David Lang wrote:
These don't look bad to me.
note that you only have an action queue for one of your actions (action2),
all the rest of your actions are being handled by the main thread. I don't
think this is what you intended (unless there really is something special
about your 'pdc' logs)
Given the main queue stats, I'd say that running any file logging process
on a dedicated queue just wastes CPU cycles and does no good.
This is why I came to the conclusion that the only potential bottleneck I
see is how fast imudp can pull out messages from the OS receive buffers. In
my experience, failure here does not even manifest in increased CPU use by
the imudp thread.
I know you said that you don't think it's DNS lookups, but am I correct in
thinking that if it is a problem with DNS lookups you would have the same
symptoms? the imudp thread would not be eating CPU as it's blocked waiting
for the response from the DNS server.
I wonder if there's a way to run more than one imudp thread on the port. the
inbound packets would not be evenly split between them, but if one is
stalled, the other may be able to pull a packet.
although I'll note that we don't know if the imudp thread is using 100% cpu or
not, it may be.
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.
