From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-pre10
Date: 02 Aug 2003 20:28:46 +0200 [thread overview]
Message-ID: <1059848925.1869.22.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <20030802181007.GB13525@alpha.home.local>
On Sat, 2003-08-02 at 20:10, Willy Tarreau wrote:
> > Have you tried using the ULOG target and the ulogd userspace daemon?
> > It uses netlink and can batch several entries together before it sends
> > them to userspace. Works a lot better than syslog.
>
> yes, I tried it about february. I thought it to be the ideal solution, and it
> performed better than the standard syslog, but not as well as syslog-ng. I
> could catch about 1500 lines/s at most, and the daemon was very hungry, it ate
> between 55 and 70% of the CPU, while syslog-ng eats about 25-30. So I thought
> it was still a bit experimental and switched to syslog-ng.
Uhm, my tests have shown it to be very fast and efficient. But I didn't
look to see if all packets got through to the logfile. But getting it to
write logs at ~35MB/s wasn't a problem.
Did you specify --ulog-qthreshold 50 ?
and did you specify --ulog-cprange at all? if you don't it will copy the
entire packet to userspace. I copy 64 bytes to userspace and that's more
than enough to log everything needed.
> > Are you using ip_conntrack on that machine? if you are, be aware that
> > ip_conntrack doesn't scale well at all on SMP. It's beeing worked on.
>
> Yes I do. I noticed the scalability problems a long time ago on my dual athlon
> at home, but wasn't really concerned. At my customer's, the only SMP one is
> used as a development gateway. All the others are UP (PIII/1G, P4/2.4G).
Ok, we are working on memory-usage and scalability stuff.
> BTW, I get the same numbers with 2.4.22-pre10 / standard ip_conntrack as with
> 2.4.21-rc2 with tcp_window_tracking. I would have thought that
> tcp_window_tracking costs a bit more, but it doesn't seem to be noticeable here.
It should cost a little bit more but not very much.
--
/Martin
next prev parent reply other threads:[~2003-08-02 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 16:19 Linux 2.4.22-pre10 Marcelo Tosatti
2003-08-01 22:47 ` Willy Tarreau
2003-08-02 9:42 ` Martin Josefsson
2003-08-02 18:10 ` Willy Tarreau
2003-08-02 18:28 ` Martin Josefsson [this message]
2003-08-02 19:14 ` Willy Tarreau
2003-08-05 12:46 ` Marcelo Tosatti
2003-08-02 13:06 ` Stephan von Krawczynski
2003-08-03 11:01 ` [2.4 patch] fix a compile warning in acpi/system.c Adrian Bunk
2003-08-03 13:16 ` [patch] 2.4.22-pre10: fix circular dependency Adrian Bunk
2003-08-05 20:19 ` Marc-Christian Petersen
2003-08-02 7:26 Linux 2.4.22-pre10 Margit Schubert-While
2003-08-02 12:13 Fridtjof Busse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1059848925.1869.22.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).