[rsyslog-notify] Forum Thread: Re: Dequeue Perfomance - (Mode 'reply')

noreply at adiscon.com noreply at adiscon.com
Mon May 4 07:27:05 CEST 2015


User: kamermans 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25475#p25475

Message: 
----------
Good tips.  

I've actually got a pretty good feel for how much memory is used per
message since I have the memory graph and pstats data from the event where
I overran the queue twice.  It turns out that my system averages about 1.5k
of RAM per message, which is probably 2 or 3 times larger than the number
of ASCII chars in the message, but still totally manageable if I know how
to set the config properly :)

With regards to performance, my CPU is just above idle, even when rsyslog
is backing up like crazy and OOMing itself, so I'm not sure what else I
should try if CPU and I/O are under 1%.  That's my motivation for
partitioning the queues.  My thinking is that the input takes a hit from
the main q transfer, but the dequeue gets a major boost since the work is
split in half.


More information about the rsyslog-notify mailing list