From: LA Walsh <law@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Jens Axboe <axboe@suse.de>
Subject: 2.4.2-test1 better on disk lock/freezups
Date: Sun, 04 Feb 2001 22:12:36 -0800 [thread overview]
Message-ID: <3A7E4454.82DDB73C@sgi.com> (raw)
In trying to apply Jens's patch I upgraded to 2.4.2-pre1. The figures on it(242-p1) look
better at this point: a vmstat dump, same data...notice this time it only took maybe 45
seconds to write out the data. I also got better interactive performance.
So write speed is up to about 3.5Mb/s. Fastest reads using 'hdparm' are in the 12-14Mb/s
range. Sooo...IDE hdparm block dev read vs. file writes...3-4:1 ratio?
I honestly have little clue as to what would be considered 'good' numbers.
Note the maximum 'system freeze' seems under 10 seconds now -- alot more
tolerable.
Note also, this was without my applying Jens's patch -- as I could not figure out how
to get it to apply cleanly :-(.
0 0 0 0 77564 80220 280164 0 0 0 348 287 1367 10 7 83
0 0 1 0 77560 80220 280164 0 0 0 304 193 225 0 1 99
0 1 1 0 77572 80220 280156 0 0 0 162 241 354 4 2 95
0 1 1 0 77572 80220 280156 0 0 0 156 218 182 0 1 99
1 1 1 0 77560 80220 280164 0 0 0 165 217 218 0 1 99
0 1 1 0 77328 80220 280164 0 0 0 134 213 215 1 1 97
0 1 1 0 77328 80220 280164 0 0 0 138 217 177 0 1 98
0 1 1 0 77328 80220 280164 0 0 0 206 215 178 0 1 99
0 1 1 0 77332 80220 280164 0 0 0 166 219 206 1 1 98
0 0 0 0 85632 80220 280172 0 0 14 12 192 360 1 1 98
--
Linda A Walsh | Trust Technology, Core Linux, SGI
law@sgi.com | Voice: (650) 933-5338
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-02-05 6:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A7E4454.82DDB73C@sgi.com \
--to=law@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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