linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: venom@sns.it
Cc: Dave Olien <dmo@osdl.org>,
	rwhron@earthlink.net, linux-kernel@vger.kernel.org,
	akpm@osdl.org
Subject: Re: [BENCHMARK] I/O regression after 2.6.0-test5
Date: Tue, 21 Oct 2003 14:49:35 +1000	[thread overview]
Message-ID: <3F94BADF.6040104@cyberone.com.au> (raw)
In-Reply-To: <Pine.LNX.4.43.0310200953480.26518-100000@cibs9.sns.it>

Hi Guys,
If you have time, would you please try testing as-iosched.c from
test5 in a later kernel (it won't go into test8-mm1 though).

Thanks


venom@sns.it wrote:

>me too, on some self made db benchs on both mysql and postgresql,  testing, of
>course, I/O.
>
>On Sun, 19 Oct 2003, Dave Olien wrote:
>
>
>>Date: Sun, 19 Oct 2003 21:51:23 -0700
>>From: Dave Olien <dmo@osdl.org>
>>To: rwhron@earthlink.net
>>Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
>>Subject: Re: [BENCHMARK] I/O regression after 2.6.0-test5
>>
>>
>>Yup, we've seen similar regression on tiobench and reaim workloads.
>>
>>On Sun, Oct 19, 2003 at 08:37:45PM -0400, 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.
>>>
>>>      
>>>


  reply	other threads:[~2003-10-21  4:49 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
2003-10-20  4:51 ` Dave Olien
2003-10-20  7:55   ` venom
2003-10-21  4:49     ` Nick Piggin [this message]
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=3F94BADF.6040104@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@osdl.org \
    --cc=dmo@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhron@earthlink.net \
    --cc=venom@sns.it \
    /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).