public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: markw@osdl.org
To: mkoi-pg@aon.at
Cc: linux-lvm@redhat.com, linux-ia64@vger.kernel.org,
	pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] PostgreSQL block size vs. LVM2 stripe width
Date: Mon, 29 Mar 2004 16:50:42 +0000	[thread overview]
Message-ID: <200403291650.i2TGop212446@mail.osdl.org> (raw)
In-Reply-To: <06sb60hni6h5cok941gqnuo4ld1b0v1rgi@email.aon.at>
In-Reply-To: <06sb60hni6h5cok941gqnuo4ld1b0v1rgi@email.aon.at>

Hi Manfred,

On 27 Mar, Manfred Koizar wrote:
> Mark,
> 
> how often did you run your tests?  Are the results reproduceable?

In this case, I've only done 1 per each combination.  I've found the
results for this test to be reproduceable.
 
> On Fri, 26 Mar 2004 14:00:01 -0800 (PST), markw@osdl.org wrote:
>>                        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
> 
> Unless someone can present at least an idea of a theory why a BLCKSZ of
> 8 KB is at a local minimum (1 or 2% below the neighbouring values) for
> stripe widths up to 64 KB I'm not sure whether we can trust these
> numbers.
> 
> Before I hit the send button, I did a quick check of the link you
> provided.  The links in the table contain the following test numbers:
> 
>         16 KB   32 KB   64 KB   128 KB  256 KB  512 KB
> 2 KB     72      71      70       69      66      65
> 4 KB     64      63      62       61      60      58
> 8 KB     54      53      52       51      50      49
> 16 KB    79      78      77       76      75      74
> 32 KB    86      85      84       83      82      80
> 
> Does this mean that you first ran all test with 8 KB, then with 4, 2, 16
> and 32 KB BLCKSZ?  If so, I suspect that you are measuring the effects
> of something different.

Yes, that's correct, but why do you suspect that?

Mark

  reply	other threads:[~2004-03-29 16:50 UTC|newest]

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