public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ben Greear <greearb@candelatech.com>,
	Christian Schmid <webmaster@rapidforum.com>,
	linux-kernel@vger.kernel.org
Subject: Re: BUG: Slowdown on 3000 socket-machines tracked down
Date: Mon, 7 Mar 2005 06:30:32 +0100	[thread overview]
Message-ID: <20050307053032.GA30052@alpha.home.local> (raw)
In-Reply-To: <422BE33D.5080904@yahoo.com.au>

On Mon, Mar 07, 2005 at 04:14:37PM +1100, Nick Piggin wrote:
 
> I think you would have better luck in reproducing this problem if you
> did the full sendfile thing.
> 
> I think it is becoming disk bound due to page reclaim problems, which
> is causing the slowdown.
> 
> In that case, writing the network only test would help to confirm the
> problem is not a networking one - so not useless by any means.

Not necessarily, Nick. I have written an HTTP testing tool which matches
the description of Ben's : non-blocking, single-threaded, no disk I/O,
etc... It works flawlessly under 2.4, and gives me random numbers in 2.6,
especially if I start some CPU activity on the system, I can get pauses
of up to 13 seconds without this tool doing anything !!! At first I
believed it was because of the scheduler, but it might also be related
to what is described here since I had somewhat the same setup (gigE, 1500,
thousands of sockets). I never had enough time to investigate more, so I
went back to 2.4.

It makes me think that for the problem described here, we have no
indication of CPU & I/O activity, which might help Ben try to reproduce.

Cheers,
Willy


  reply	other threads:[~2005-03-07  5:30 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 [this message]
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
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=20050307053032.GA30052@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=webmaster@rapidforum.com \
    /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