[syslog-ng] 3.4 - degraded single threaded performance

[Balazs Scheidler]

----- Original message -----
> Evan Rempel <erempel at uvic.ca> writes:
> 
> > I took one of my syslog-ng 3.3 configuraiton files, which happens to
> > read from a named pipe (/var/local/somename) and ran version 3.4rc2
> > against it.
> > 
> > I was only able toread bout 2,000 messages/sec through the pipe.
> > With threaded(yes) I could read 100,000+/sec.
> > With syslog-ng 3.3 I could read 100,000+/sec
> > 
> > Is this the expected behaviour of threaded(no) with syslog-ng 3.4
> 
> Nope, it definitely is not.
> 

sounds like a bug to me too. I wonder how a perf output would look like.

Does it saturate the cpu at 100% while this happens?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20130121/b4f4a9b8/attachment.htm