From: Christian Schmid <webmaster@rapidforum.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, linux-kernel@vger.kernel.org
Subject: Re: BUG: Slowdown on 3000 socket-machines tracked down
Date: Thu, 10 Mar 2005 00:52:56 +0100 [thread overview]
Message-ID: <422F8C58.4000809@rapidforum.com> (raw)
In-Reply-To: <422F8A8A.8010606@candelatech.com>
> Yes, 2.6.11. I have tuned max_backlog and some other TCP and networking
> related settings to give more buffers etc to networking tasks. I have not
> tried any significant disk-IO while doing these tests.
>
> I finally got my systems set up so I can run my WAN emulator at full 1Gbps:
>
> I am getting right at 986Mbps throughput with 30ms round-trip latency
> (15ms in both directions).
>
> So, latency does not seem to be the problem either.
>
> I think the problem can be narrowed down to:
>
> 1) Non-optimal kernel network tunings on your server.
I used all the default-settings on 2.6.11
> 2) Disk-IO (my disk is small and slow compared to a 'real' server, not
> sure I can
> really test this side of things, and I have not tried as of yet.)
This doesnt explain the speed-up when I change lower_zone_protection from 0 to 1024. It also doesnt
explain the slowdown on 2.6.11 compared to 2.6.10
> 3) Your clients have much more latency and/or don't have enough bandwidth
> to fully load your server. Since you didn't answer before: I
> assume you
> do not have a reliable test bed and are just hoping that enough
> clients connect
> to do your benchmarking.
Yes I just wait until they connect. On the graph it only takes about 2 minutes until 3000 sockets
are created again.
> 4) There is something strange with sendfile and/or your application's
> coding.
I am not doing more than calling sendfile. There is nothing one can do wrong.
> My suggestion would be to eliminate these variables by coming up with a
> repeatable
> test bed, alternative traffic generators, WAN/Network emulators for
> latency, etc.
The problem still is that 1) it speeds up immediately when lower_zone_protection is raised to 1024.
This proves it is NOT a disk-bottleneck. And second: it got much worse with 2.6.11 and
lower_zone_protection disappeared on 2.6.11
Chris
next prev parent reply other threads:[~2005-03-09 23:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 17:10 BUG: Slowdown on 3000 socket-machines tracked down Christian Schmid
2005-03-07 0:45 ` Nick Piggin
2005-03-07 1:13 ` Ben Greear
2005-03-07 1:58 ` Christian Schmid
2005-03-07 2:57 ` Ben Greear
2005-03-07 5:14 ` Nick Piggin
2005-03-07 5:30 ` Willy Tarreau
2005-03-07 5:41 ` Nick Piggin
2005-03-07 5:42 ` Nick Piggin
2005-03-07 5:46 ` Willy Tarreau
2005-03-07 9:22 ` Ben Greear
2005-03-07 9:28 ` Nick Piggin
2005-03-08 6:30 ` Ben Greear
2005-03-08 16:41 ` Christian Schmid
2005-03-09 23:45 ` Ben Greear
2005-03-09 23:52 ` Christian Schmid [this message]
2005-03-10 0:18 ` Ben Greear
2005-03-10 0:24 ` Christian Schmid
2005-03-10 5:17 ` Andrew Morton
2005-03-10 9:00 ` Andi Kleen
2005-03-10 9:09 ` Andrew Morton
2005-03-10 9:12 ` Andi Kleen
2005-03-10 9:38 ` Andrew Morton
2005-03-10 19:03 ` Ben Greear
2005-03-10 18:51 ` Christian Schmid
2005-03-10 19:06 ` Christian Schmid
2005-03-11 15:29 ` Christian Schmid
2005-03-11 19:10 ` Ben Greear
2005-03-11 19:27 ` Christian Schmid
2005-03-14 4:40 ` Nick Piggin
2005-03-14 4:53 ` Christian Schmid
2005-03-14 5:04 ` Nick Piggin
2005-05-28 3:17 ` Christian Schmid
2005-06-08 2:26 ` Christian Schmid
2005-06-08 2:39 ` Nick Piggin
2005-06-08 2:44 ` Andrew Morton
2005-03-07 14:35 ` Christian Schmid
2005-03-07 23:37 ` Ben Greear
2005-03-07 2:07 ` Christian Schmid
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=422F8C58.4000809@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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