From: Samium Gromoff <deepfire@ibe.miee.ru>
To: Samium Gromoff <deepfire@ibe.miee.ru>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com, wli@holomorphy.com,
andrea@suse.de
Subject: Re: [VM] writes starve reads in 2.5.72-bk1
Date: Mon, 30 Jun 2003 10:09:22 +0400 [thread overview]
Message-ID: <20030630100922.26db2333.deepfire@ibe.miee.ru> (raw)
In-Reply-To: <20030630100258.3c17ee04.deepfire@ibe.miee.ru>
On Mon, 30 Jun 2003 10:02:58 +0400
Samium Gromoff <deepfire@ibe.miee.ru> wrote:
> load: gzipping a 128M file, with "gzip file"
> CPU: p3-500
> physical RAM installed: 256M
> kernel: 2.5.72-bk1
> drive: one 10krpm IBM
> controller: DAC960PL RAID controller
>
> 0 1 9384 3960 33640 116184 0 0 1280 4096 1022 122 63 7 0 30
> 1 0 9384 4016 33220 116568 0 0 1792 0 1096 122 81 7 0 12
> 1 0 9384 3624 33156 117112 0 0 2048 0 1036 119 92 8 0 0
> 1 1 9384 4856 32024 116876 0 0 1024 11432 1092 145 48 5 2 44
> 0 2 9384 4632 32024 117164 0 0 128 7288 1120 208 8 2 0 90
> 0 2 9384 4072 32024 117676 0 0 256 9172 1149 224 12 2 0 86
> 1 0 9384 3624 31516 118684 0 0 896 944 1146 145 38 4 0 58
> 1 0 9384 3288 30916 119764 0 0 2048 0 1031 117 92 8 0 0
> 1 0 9384 4128 30620 119228 0 0 1920 92 1062 160 92 7 1 0
> 1 0 9384 3960 30208 120120 0 0 2048 0 1033 115 93 7 0 0
> procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
> r b swpd free buff cache si so bi bo in cs us sy id wa
>
> problem as i see it:
>
> although the drive is mostly idle since the cpu is too slow to max it out,
> reads are starved during bursts of gzipped data writeouts,
> causing gzip to spend its time on sleeping on request completion.
Now i notice that the anticipatory sheduler isn`t in the mainline...
So all this sounds a little bit old...
Anyways, hope it helps...
>
> regards, Samium Gromoff
--
prev parent reply other threads:[~2003-06-30 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 6:02 Samium Gromoff
2003-06-30 6:09 ` Samium Gromoff [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=20030630100922.26db2333.deepfire@ibe.miee.ru \
--to=deepfire@ibe.miee.ru \
--cc=akpm@digeo.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®