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

[noreply at adiscon.com]

User: dlang 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25474#p25474

Message: 
----------
One problem we have seen is that if every single action has it's own queue,
rsyslog can end up spending a lot of cpu shuffling messages around
(especially if you define multiple worker threads on the main queue). It's
actually better if the worker thread has some real work to do (it's
activity moving the messages from the main queue to the action queues ends
up keeping the main queue locked too much of the time, making it harder for
the input modules to add new messages, if it has work to do, it instead
processes messages in batches and the main queue is locked less of the
time)

But you have the right basic idea

don't forget that the main queue needs ram as well.

test your max memory by blocking the outputs and feeding it data until it
stops accepting new data (at which pint all the queues should be full), us
pstats to see your queue and resource usage