From: Christian Schmid <webmaster@rapidforum.com>
To: Andrew Morton <akpm@osdl.org>
Cc: greearb@candelatech.com, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org
Subject: Re: BUG: Slowdown on 3000 socket-machines tracked down
Date: Fri, 11 Mar 2005 16:29:31 +0100 [thread overview]
Message-ID: <4231B95B.6020209@rapidforum.com> (raw)
In-Reply-To: <20050309211730.24b4fc93.akpm@osdl.org>
OHGAWD I GOT IT!!!!!!!!
I admit, totally coincidentially but its really FIXED. Today I went to the puter scanning the
servers by routine and wondered why the bandwidth is at 100% without any holes.
The only thing I have done is I switched off hyper-threading because the server is at only 20% CPU
anyway so I just disabled it.
So its something with linux dealing with hyper-threading. YAY :)
Andrew Morton wrote:
> Christian Schmid <webmaster@rapidforum.com> wrote:
>
>> > So, maybe a VM problem? That would be a good place to focus since
>> > I think we can be fairly certain it isn't a problem in just the
>> > networking code. Otherwise, my tests would show lower bandwidth.
>>
>> Thanks to your tests I am really sure that its no network-code problem anymore. But what I THINK it
>> is: The network is allocating buffers dynamically and if the vm doesnt provide that buffers fast
>> enough, it locks as well.
>
>
> Did anyone have a 100-liner which demonstrates this problem?
>
> The output of `vmstat 1' when the thing starts happening would be interesting.
>
>
next prev parent reply other threads:[~2005-03-11 15:29 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
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 [this message]
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=4231B95B.6020209@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.