From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] I/O regression after 2.6.0-test5
Date: Mon, 20 Oct 2003 18:12:11 +1000 [thread overview]
Message-ID: <3F9398DB.8030004@cyberone.com.au> (raw)
In-Reply-To: <20031019215259.7b1c7a01.akpm@osdl.org>
Andrew Morton wrote:
>Nick Piggin <piggin@cyberone.com.au> wrote:
>
>>
>>
>>rwhron@earthlink.net wrote:
>>
>>
>>>There was about a 50% regression in jobs/minute in AIM7
>>>database workload on quad P3 Xeon. The CPU time has not
>>>gone up, so the extra run time is coming from something
>>>else. (I/O or I/O scheduler?)
>>>
>>>tiobench sequential reads has a significant regression too.
>>>
>>>Regression appears unrelated to filesystem type.
>>>
>>>dbench was not affected.
>>>
>>>The AIM7 was run on ext2.
>>>
>>>
>>Yeah I'd say its all due to the IO scheduler. There is a problem
>>I'm thinking about how to fix - its the likely cause of this too.
>>
>>
>
>What change do you think it was due to?
>
>
I was thinking: [PATCH] fix AS crappy performance
(It still doesn't work properly)
>It's rather strange that test6 is slow but test6-mm is not: generally the
>IO scheduler regressions enter -mm first ;)
>
But if test6-mm isn't slow then maybe it is due to something else
next prev parent reply other threads:[~2003-10-20 8:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 0:37 [BENCHMARK] I/O regression after 2.6.0-test5 rwhron
2003-10-20 1:35 ` Nick Piggin
2003-10-20 4:52 ` Andrew Morton
2003-10-20 8:12 ` Nick Piggin [this message]
2003-10-20 4:51 ` Dave Olien
2003-10-20 7:55 ` venom
2003-10-21 4:49 ` Nick Piggin
2003-10-24 13:52 ` Magnus Andersson
2003-10-21 13:05 rwhron
2003-10-21 15:57 ` Nick Piggin
2003-10-21 21:07 ` venom
2003-10-22 9:54 ` Nick Piggin
2003-10-22 18:30 ` Dave Olien
2003-10-22 19:08 ` Dave Olien
2003-10-23 2:24 ` Nick Piggin
2003-10-23 3:48 ` Nick Piggin
2003-10-23 20:35 ` Dave Olien
2003-10-23 23:07 ` Nick Piggin
2003-10-24 0:10 rwhron
2003-10-24 12:46 rwhron
2003-10-24 23:43 rwhron
2003-10-26 10:38 rwhron
2003-10-27 23:49 ` Dave Olien
2003-10-27 23:33 John Hawkes
2003-10-29 0:38 rwhron
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=3F9398DB.8030004@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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).