From: Ingo Molnar <mingo@elte.hu>
To: markw@osdl.org
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au
Subject: Re: 2.6.5-mm5
Date: Fri, 16 Apr 2004 12:34:14 +0200 [thread overview]
Message-ID: <20040416103414.GA736@elte.hu> (raw)
In-Reply-To: <200404151530.i3FFUI226872@mail.osdl.org>
* markw@osdl.org <markw@osdl.org> wrote:
> I have more results with DBT-2 on my 4-way Xeon system:
> http://developer.osdl.org/markw/fs/dbt2_project_results.html
>
> It doesn't look like the latest cpu scheduler work is helping this
> workload. I've also made sure that the database was set to use fsync
> instead of fdatasync so you can see if those fsync speedup patches are
> offering anything with this workload too.
>
> ext2 ext3
> 2.6.5-mm5 2165 1933
> 2.6.5-mm4 2180
> 2.6.5-mm3 2165 1930
> 2.6.5 2385
how stable are the results? Could the 2180 => 2165 drop be noise?
Ingo
next prev parent reply other threads:[~2004-04-16 10:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 5:17 2.6.5-mm5 Andrew Morton
2004-04-13 7:38 ` 2.6.5-mm5 Kurt Fitzner
2004-04-13 7:56 ` 2.6.5-mm5 Nick Piggin
2004-04-13 8:07 ` 2.6.5-mm5 devpts filesystem doesn't work Helge Hafting
2004-04-13 8:11 ` Andrew Morton
2004-04-13 8:36 ` Sean Neakums
2004-04-13 8:39 ` Andrew Morton
2004-04-13 9:19 ` Marc-Christian Petersen
2004-04-13 9:26 ` Andrew Morton
2004-04-14 12:38 ` Helge Hafting
2004-04-13 11:36 ` 2.6.5-mm5: no help text for S2IO_NAPI Adrian Bunk
2004-04-13 16:02 ` 2.6.5-mm5 (compile stats) John Cherry
2004-04-15 15:30 ` 2.6.5-mm5 markw
2004-04-15 19:42 ` 2.6.5-mm5 Andrew Morton
2004-04-16 14:51 ` 2.6.5-mm5 markw
2004-04-16 22:59 ` 2.6.5-mm5 Nick Piggin
2004-04-16 23:03 ` 2.6.5-mm5 markw
2004-04-18 9:20 ` 2.6.5-mm5 Nick Piggin
2004-04-19 14:53 ` 2.6.5-mm5 markw
2004-04-19 14:51 ` 2.6.5-mm5 markw
2004-04-16 1:57 ` 2.6.5-mm5 Nick Piggin
2004-04-16 10:34 ` Ingo Molnar [this message]
2004-04-16 14:52 ` 2.6.5-mm5 markw
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=20040416103414.GA736@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.org \
--cc=nickpiggin@yahoo.com.au \
/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