All of lore.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: Mon, 28 Feb 2005 19:56:44 +0100	[thread overview]
Message-ID: <4223696C.8060407@rapidforum.com> (raw)
In-Reply-To: <4222A887.80301@yahoo.com.au>

This issue has been tracked down more. This bug does NOT appear if I disable preemtive kernel.
Maybe this helps.

Nick Piggin wrote:
> Christian Schmid wrote:
> 
>> I already tried with 300 KB and even used a perl-hash as a 
>> horrible-slow buffer for a readahead-replacement. It still slowed down 
>> on the syswrite to the socket. Thats the strange thing.
>>
> 
> Do you have to use manual readahead though? What is the performance
> like if you just let the kernel do its own thing? The kernel's
> readahead provides things like automatic scaling and thrashing
> control, so if possible you should just stick to that.
> 
> Although you may want to experiment with the maximum readahead on your
> working disks:
> /sys/block/???/queue/read_ahead_kb
> 
> Also, can we get a testcase (ie. minimal compilable code) to reproduce
> this problem?
> 
> Thanks,
> Nick
> 
> 
> 

  parent reply	other threads:[~2005-02-28 19:06 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 [this message]
2005-02-28 23:46                   ` Nick Piggin
2005-03-05 16:39                     ` 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=4223696C.8060407@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 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.