public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Schmid <webmaster@rapidforum.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Rik van Riel <riel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Slowdown on high-load machines with 3000 sockets
Date: Sat, 05 Mar 2005 17:39:44 +0100	[thread overview]
Message-ID: <4229E0D0.9000508@rapidforum.com> (raw)
In-Reply-To: <4223AD5F.1090500@yahoo.com.au>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

Attached is another traffic-image. This one is with 2.6.10 and a 3/1 split, preemtive kernel, so all 
defaults.

The first part is where I throttled the whole thing to 100 MBit in order to build up a traffic-jam ;)

When I released it, it jumped up immediately but suddenly it goes down (each pixel is one second) 
Playing around with min_free_kbytes didnt help. Where it goes up again I set lower_zone_protection 
to 1024000 and where it goes down I set it to 0 again and where it goes up the last time... guess..

Well I was only able to test this with 3500 sockets. I will try to jam up tomorrow to reach 5000 
sockets to see if that is really the reason.

Nick Piggin wrote:
> Christian Schmid wrote:
> 
>> This issue has been tracked down more. This bug does NOT appear if I 
>> disable preemtive kernel.
>> Maybe this helps.
>>
> 
> Yes, it may help - can you boot with profile=schedule and get
> the results for say, a 30 second period while the application
> is experiencing problems?
> 
> So:
> 
> start application
> wait till it hits slowdown
> readprofile -r ; sleep 30 ; readprofile > schedprof.out
> 
> and send schedprof.out, please?
> 
> Thanks,
> Nick
> 
> 
> 

[-- Attachment #2: traffic2.png --]
[-- Type: image/png, Size: 2504 bytes --]

      reply	other threads:[~2005-03-05 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 16:53 Slowdown on high-load machines with 3000 sockets Christian Schmid
2005-02-27 17:18 ` Rik van Riel
2005-02-27 21:09   ` Rik van Riel
2005-02-27 21:20     ` Christian Schmid
2005-02-27 23:32       ` Rik van Riel
2005-02-27 23:43         ` Christian Schmid
2005-02-28  0:06           ` Rik van Riel
2005-02-28  0:29             ` Christian Schmid
2005-02-28  5:13               ` Nick Piggin
2005-02-28 11:36                 ` Christian Schmid
2005-02-28 18:56                 ` Christian Schmid
2005-02-28 23:46                   ` Nick Piggin
2005-03-05 16:39                     ` Christian Schmid [this message]

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=4229E0D0.9000508@rapidforum.com \
    --to=webmaster@rapidforum.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.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