From: Bill Davidsen <davidsen@tmr.com>
To: markw@osdl.org
Cc: linux-lvm@redhat.com, linux-kernel@vger.kernel.org
Subject: [linux-lvm] Re: lvm2 performance data with linux-2.6
Date: Fri Mar 12 10:38:02 2004 [thread overview]
Message-ID: <4050E453.3010809@tmr.com> (raw)
In-Reply-To: <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/
>
> So far I've only varied the stripe width with lvm, from 8 KB to 512 KB,
> for PostgreSQL that is using 8 KB sized blocks with ext2. It appears
> that a stripe width of 16 KB through 128KB on the ia64 system gives the
> best throughput for the DBT-2 workload on a volume that should be doing
> mostly sequential writes.
>
> I'm going to run through more tests varying the block size that
> PostgreSQL uses, but I wanted to share what I had so far in case there
> were other suggestions or recommendations.
>
Here's one thought: look at the i/o rates on individual drives using
each stripe size. You *might* see that one size does far fewer seeks
than others, which is a secondary thing to optimize after throughput IMHO.
If you don't have a tool for this I can send you the latest diorate
which does stuff like this, io rate perdrive or per partition, something
I occasionally find revealing.
-bill
WARNING: multiple messages have this Message-ID (diff)
From: Bill Davidsen <davidsen@tmr.com>
To: markw@osdl.org
Cc: linux-lvm@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: lvm2 performance data with linux-2.6
Date: Thu, 11 Mar 2004 17:12:35 -0500 [thread overview]
Message-ID: <4050E453.3010809@tmr.com> (raw)
In-Reply-To: <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/
>
> So far I've only varied the stripe width with lvm, from 8 KB to 512 KB,
> for PostgreSQL that is using 8 KB sized blocks with ext2. It appears
> that a stripe width of 16 KB through 128KB on the ia64 system gives the
> best throughput for the DBT-2 workload on a volume that should be doing
> mostly sequential writes.
>
> I'm going to run through more tests varying the block size that
> PostgreSQL uses, but I wanted to share what I had so far in case there
> were other suggestions or recommendations.
>
Here's one thought: look at the i/o rates on individual drives using
each stripe size. You *might* see that one size does far fewer seeks
than others, which is a secondary thing to optimize after throughput IMHO.
If you don't have a tool for this I can send you the latest diorate
which does stuff like this, io rate perdrive or per partition, something
I occasionally find revealing.
-bill
next prev parent reply other threads:[~2004-03-11 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 14:15 [linux-lvm] lvm2 performance data with linux-2.6 markw
2004-03-08 19:16 ` markw
2004-03-08 19:46 ` Miquel van Smoorenburg
2004-03-08 22:01 ` Matthias Andree
2004-03-11 22:12 ` Bill Davidsen [this message]
2004-03-12 10:38 ` [linux-lvm] " Bill Davidsen
2004-03-11 17:23 ` Mark Wong
2004-03-11 22:25 ` Mark Wong
2004-03-11 18:01 ` [linux-lvm] " Chris Croswhite
2004-03-11 23:01 ` Chris Croswhite
2004-03-14 14:02 ` Bill Davidsen
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=4050E453.3010809@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=markw@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.