<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>----- Original message -----
<br>> Evan Rempel <<a href="mailto:erempel@uvic.ca">erempel@uvic.ca</a>> writes:
<br>>
<br>> > I took one of my syslog-ng 3.3 configuraiton files, which happens to
<br>> > read from a named pipe (/var/local/somename) and ran version 3.4rc2
<br>> > against it.
<br>> >
<br>> > I was only able toread bout 2,000 messages/sec through the pipe.
<br>> > With threaded(yes) I could read 100,000+/sec.
<br>> > With syslog-ng 3.3 I could read 100,000+/sec
<br>> >
<br>> > Is this the expected behaviour of threaded(no) with syslog-ng 3.4
<br>>
<br>> Nope, it definitely is not.
<br>>
<br>
<br>sounds like a bug to me too. I wonder how a perf output would look like.
<br>
<br>Does it saturate the cpu at 100% while this happens?
<br><br></p>
</body>
</html>