From: Apurva Mehta <apurva@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2-mm2
Date: Fri, 1 Aug 2003 01:07:41 +0530 [thread overview]
Message-ID: <20030731193741.GA1618@home.woodlands> (raw)
In-Reply-To: <20030730223810.613755b4.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> [31-07-2003 14:52]:
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test2/2.6.0-test2-mm2/
>
> . CPU scheduler changes
>
> . Several changes to the synaptics and PS/2 drivers. People who have had
> problems with keyboards and mice, please test and report.
>
> . Lots of other things, mainly bugfixes.
I have noticed that while the system remains responsive when there is
heavy CPU load alone, the unresponsiveness comes when there is heavy disk
i/o. In light of this, I subjected my system to the following tests :
1) Untarred linux-2.6.0-test2.tar.bz2 (To create a stream of writes)
2) did a `find / -name "foobar" -print` as root (To create a stream of reads)
3) bzip2'ed a 30 MB file to 3.2 MB ( this ensures 100 % CPU usage).
All the above were working on the same disk.
As the above three things were going on, I was browsing, playing music
on xmms, reading a pdf file in acrobat and generally switching between
windows.
I did the above test on both 2.6.0-test2-mm1 + O11int + O11.1int ( no
O11.2 int) and on 2.6.0-test2-mm2. I find that mm1 + O11 patches are
better than mm2. The music never skipped on mm1, while it did on
mm2. Also, overall resposiveness of the various windows was better on
mm1.
However, when I did a `rpm --rebuilddb` on mm1 + O11int patches, I
still got quite severe skipping toward the end of the 8 min process. I
could not repeat the skipping again, even on the same kernel, because
I guess there was not much rebuilding to do again..
If there are tools which I can use to produce helpful numbers, please
let me know. I will post the required numbers ASAP.
Also, if you have any other tests which I could perform to create
heavy disk I/O, please let me know about that too.
Regards,
- Apurva
next prev parent reply other threads:[~2003-07-31 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 5:38 2.6.0-test2-mm2 Andrew Morton
2003-07-31 9:50 ` 2.6.0-test2-mm2 Peter Osterlund
2003-07-31 10:57 ` 2.6.0-test2-mm2 Ramón Rey Vicente
2003-08-01 11:00 ` 2.6.0-test2-mm2 Jose Luis Domingo Lopez
2003-07-31 15:06 ` 2.6.0-test2-mm2: BTTV build error Adrian Bunk
2003-08-04 9:13 ` Gerd Knorr
2003-08-09 20:01 ` Adrian Bunk
2003-07-31 19:37 ` Apurva Mehta [this message]
2003-07-31 20:33 ` 2.6.0-test2-mm2 Mike Fedyk
2003-08-02 15:19 ` 2.6.0-test2-mm2 Dave Jones
2003-08-02 19:04 ` 2.6.0-test2-mm2 Andrew Morton
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=20030731193741.GA1618@home.woodlands \
--to=apurva@gmx.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;
as well as URLs for NNTP newsgroup(s).