From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Subject: Is Andrew Morton a god?
Date: Sat, 1 Dec 2001 03:49:58 -0500 [thread overview]
Message-ID: <20011201034958.A4354@earthlink.net> (raw)
Something beautiful has happened in 2.4.17-pre2.
Interactive Latency during very heavy disk I/O has dropped dramatically.
Several LTP tests have a tendency to make interactive performance poor.
The improvement in 2.4.17-pre2 is astonishing.
Normally runalltests.sh does one test at a time. Since the usual
interactivity slowdown during the growfiles tests didn't happen, I
tried running a bunch of things at once.
Concurrently:
3 growfiles scripts (run all growfiles tests in LTP).
3 LTP runalltests.sh
setiathome
make clean dep bzImage modules
list directories with lots files that hadn't been listed before in this boot.
ps, w, logout, login.
3 irc clients, play a couple mp3s, read entertaining Coding Standards thread.
The start time of the concurrent growfiles and runalltests.sh was spaced
out, so different tests were being executed.
Occasionally ls or w had a 10 second or so delay, but delays were infrequent,
and shorter than usual.
Kudos to all the Kernel Hackers!
--
Randy Hron
reply other threads:[~2001-12-01 8:47 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=20011201034958.A4354@earthlink.net \
--to=rwhron@earthlink.net \
--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