From: Christian Schmid <webmaster@rapidforum.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ben Greear <greearb@candelatech.com>,
Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG: Slowdown on 3000 socket-machines tracked down
Date: Mon, 14 Mar 2005 05:53:27 +0100 [thread overview]
Message-ID: <423518C7.10207@rapidforum.com> (raw)
In-Reply-To: <1110775215.5131.17.camel@npiggin-nld.site>
>>This effect appeared on 1 task and on 200 tasks. I dont know what it is, but with HT off it doesnt
>>appear anymore. The slow-down still appears when lower_zone_protection is set to 0 but the peak at
>>80 MB disappeared when set to 1024. I am now running at 95 MB/Sec smoothly.
>>
>
> OK well that is a good result for you. Thanks for sticking with it.
> Unfortunately you'll probably not want to test any patches on your
> production system, so the cause of the problem will be difficult to
> fix.
>
> I am working on patches which improve HT performance in some
> situations though, so with luck they will cure your problems too.
> Basically I think SMP "balancing" is too aggressive - and this may
> explain why 2.6.10 was worse for you, it had patches to *increase*
> the aggressiveness of balancing.
>
> The other thing that worries me is your need for lower_zone_protection.
> I think this may be due to unbalanced highmem vs lowmem reclaim. It
> would be interesting to know if those patches I sent you improve this.
> They certainly improve reclaim balancing for me... but again I guess
> you'll be reluctant to do much experimentation :\
I have tested your patch and unfortunately on 2.6.11 it didnt change anything :( I reported this
before, or do you mean something else? I am of course willing to test patches as I do not want to
stick with 2.6.10 forever.
next prev parent reply other threads:[~2005-03-14 4:54 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
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 [this message]
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=423518C7.10207@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.