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: Sun, 27 Feb 2005 22:20:40 +0100 [thread overview]
Message-ID: <422239A8.1090503@rapidforum.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0502271606220.19979@chimarrao.boston.redhat.com>
Rik van Riel wrote:
> On Sun, 27 Feb 2005, Rik van Riel wrote:
>
>
>>Is it possible to detect when the write system call blocks?
>
>
> OK, we got that on #kernelnewbies Initially the trace looks
> innocent enough, but there is something interesting going on
> with the VM. Something we may want to investigate...
>
> <Dragony> Feb 27 21:12:34 s02 kernel: Call Trace:
> <Dragony> Feb 27 21:12:34 s02 kernel: [<803e1148>] io_schedule+0x28/0x40
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8015ac26>] sync_buffer+0x36/0x50
> <Dragony> Feb 27 21:12:34 s02 kernel: [<803e1396>] __wait_on_bit+0x66/0x70
> <Dragony> Feb 27 21:12:34 s02 kernel: [<803e1428>] out_of_line_wait_on_bit+0x88/0x90
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8015c2a5>] __bread_slow+0x65/0x90
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8015c5bd>] __bread+0x3d/0x50
> <Dragony> Feb 27 21:12:34 s02 kernel: [<801dcdc7>] ext2_get_branch+0x77/0x120
> <Dragony> Feb 27 21:12:34 s02 kernel: [<801dd187>] ext2_get_block+0x77/0x3c0
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8017d258>] do_mpage_readpage+0x1a8/0x4f0
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8017d64f>] mpage_readpages+0xaf/0x130
> <Dragony> Feb 27 21:12:34 s02 kernel: [<80140c56>] read_pages+0xf6/0x100
> <Dragony> Feb 27 21:12:34 s02 kernel: [<80140f47>] do_page_cache_readahead+0x117/0x1a0
> <Dragony> Feb 27 21:12:34 s02 kernel: [<801411ab>] page_cache_readahead+0x1db/0x240
> <Dragony> Feb 27 21:12:34 s02 kernel: [<80139b10>] do_generic_mapping_read+0x100/0x3f0
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8013a31b>] generic_file_sendfile+0x5b/0x70
> <Dragony> Feb 27 21:12:34 s02 kernel: [<8015a4b0>] do_sendfile+0x1f0/0x2c0
>
> Looks like his program is doing a sendfile, which pauses
> on reading things from disk. So far, so good.
>
> However, the big question is why the slowdowns go away
> when min_free_kbytes is larger ?
>
> As an additional hint, Christian is using sys_readahead.
>
> 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.
next prev parent reply other threads:[~2005-02-27 21:20 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 [this message]
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
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=422239A8.1090503@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox