From: Christian Schmid <webmaster@rapidforum.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slowdown on high-load machines with 3000 sockets
Date: Mon, 28 Feb 2005 00:43:48 +0100 [thread overview]
Message-ID: <42225B34.7020104@rapidforum.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0502271830380.19979@chimarrao.boston.redhat.com>
No i am only using 4 tasks with Poll-API and non-blocking sockets. Every socket gets a 1 MB
read-ahead. This are 4000 MB Max on a 8 GB machine.... Shouldnt thrash.
Rik van Riel wrote:
> On Sun, 27 Feb 2005, Christian Schmid wrote:
>
>
>>>Christian, how big are the data blocks you sys_readahead, and
>>>how many do you have outstanding at a time ?
>>
>>I am reading 800000 bytes of data as soon as there is less than 200000
>>data in the cache. I do assume the cache doesnt kill itself. I have 8 GB
>>machine with 7,5 GB free for caching.
>
>
> OK, so you read 800kB with 4000 threads, or 3.2GB of
> readahead data. The inactive list is quite possibly
> smaller than that, at 1/3 of memory or around 2.6 GB.
>
> It looks like the cache might be killing itself, through
> readahead thrashing.
>
next prev parent reply other threads:[~2005-02-28 0:09 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 [this message]
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
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=42225B34.7020104@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=linux-kernel@vger.kernel.org \
--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.