From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: lvm2 performance data with linux-2.6
Date: Mon, 8 Mar 2004 19:46:35 +0000 (UTC) [thread overview]
Message-ID: <c2iiir$el4$1@news.cistron.nl> (raw)
In-Reply-To: 200403081916.i28JGgE25794@mail.osdl.org
In article <200403081916.i28JGgE25794@mail.osdl.org>,
<markw@osdl.org> wrote:
>I've started collecting various data (including oprofile) using our
>DBT-2 (OLTP) workload with lvm2 on linux 2.6.2 and 2.6.3 on ia32 and
>ia64 platforms:
> http://developer.osdl.org/markw/lvm2/
For write-heavy loads, you might want to see if 2.6.4-rc2-mm1 makes
any difference. It fixes a case where both pdflush and a writing
process itself would queue writes to an LVM device, resulting in
less than optimal I/O ordering for some cases. The fix will probably
be in 2.6.4 proper as well.
Mike.
next prev parent reply other threads:[~2004-03-08 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 19:16 lvm2 performance data with linux-2.6 markw
2004-03-08 19:46 ` Miquel van Smoorenburg [this message]
2004-03-08 22:01 ` Matthias Andree
2004-03-11 22:12 ` Bill Davidsen
2004-03-11 22:25 ` Mark Wong
2004-03-11 23:01 ` [linux-lvm] " Chris Croswhite
2004-03-14 14:02 ` Bill Davidsen
2004-03-16 21:42 ` bill davidsen
2004-03-16 23:17 ` 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='c2iiir$el4$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--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