public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: markw@osdl.org
To: pgsql-hackers@postgresql.org
Cc: linux-ia64@vger.kernel.org, linux-lvm@redhat.com
Subject: PostgreSQL block size vs. LVM2 stripe width
Date: Fri, 26 Mar 2004 22:00:01 +0000	[thread overview]
Message-ID: <200403262200.i2QM04223972@mail.osdl.org> (raw)

I have some results from DBT-2 testing PostgreSQL with difference block
sizes against different lvm stripe widths on Linux.  I've found that
iostat appears to report more erratic numbers as the block size of the
database increases but I'm not able to see any reason for it.

I have pg_xlog on a separate set of drives from the rest of the database
and was wondering if having different block sizes for the log and the
data has been discusses?

Or does anyone have any tips for an optimal combination of settings?

Here's a summary from an Itanium2 system, where bigger is better:

                        Linux-2.6.3, LVM2 Stripe Width
                        (going across)
PostgreSQL
BLCKSZ
(going down)    16 KB   32 KB   64 KB   128 KB  256 KB  512 KB
2 KB            2617    2656    2652    2664    2667    2642
4 KB            4393    4486    4577    4557    4511    4448
8 KB            4337    4423    4471    4576    4111    3642
16 KB           4412    4495    4532    4536    2985    2312
32 KB           3705    3784    3886    3925    2936    2362

Links to more data:
	http://developer.osdl.org/markw/lvm2/blocks.html

Mark

             reply	other threads:[~2004-03-26 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 22:00 markw [this message]
2004-03-27 22:03 ` [HACKERS] PostgreSQL block size vs. LVM2 stripe width Manfred Koizar
2004-03-29 16:50   ` markw
2004-03-29 22:42     ` Manfred Koizar
2004-03-29 22:52   ` 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=200403262200.i2QM04223972@mail.osdl.org \
    --to=markw@osdl.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-lvm@redhat.com \
    --cc=pgsql-hackers@postgresql.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