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 22:52:35 +0000 [thread overview]
Message-ID: <200403292252.i2TMqi222698@mail.osdl.org> (raw)
In-Reply-To: <5r5h60pus29i6hf4eftka319gmqlrd6ies@email.aon.at>
In-Reply-To: <06sb60hni6h5cok941gqnuo4ld1b0v1rgi@email.aon.at>
On 30 Mar, Manfred Koizar wrote:
> On Mon, 29 Mar 2004 08:50:42 -0800 (PST), markw@osdl.org wrote:
>>In this case, I've only done 1 per each combination. I've found the
>>results for this test to be reproduceable.
>
> Pardon?
I haven't repeated any runs for each combination, e.g. 1 test with 16kb
lvm stripe width and 2kb BLCKSZ, 1 test with 16kb lvm stripe width and
4kb BLCKSZ...
>>>> Linux-2.6.3, LVM2 Stripe Width
>>>>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
>
>>> 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?
>
> Gut feelings, hard to put into words. Let me try:
>
> Nobody really knows what the "optimal" BLCKSZ is. Most probably it
> depends on the application, OS, hardware, and other factors. 8 KB is
> believed to be a good general purpose BLCKSZ.
>
> I wouldn't be surprised if 8 KB turns out to be suboptimal in one or the
> other case (or even in most cases). But if so, I would expect it to be
> either too small or too large.
>
> In your tests, however, there are three configurations where 8 KB is
> slower than both 4 KB and 16 KB. Absent any explanation for this
> interesting effect, it is easier to mistrust your numbers.
>
> If you run your tests in the opposite order, on the same hardware, in
> the same freshly formatted partitions, and you get the same results,
> that would be an argument in favour of their accurancy.
>
> Maybe we find out that those 1.5% are just noise.
I did reformat each partition between tests. :) When I have tested for
repeatability in the past I have found results to fluxuate up to 5%, so
I would claim the 1.5% to be noise.
Mark
prev parent reply other threads:[~2004-03-29 22:52 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
2004-03-29 22:42 ` Manfred Koizar
2004-03-29 22:52 ` markw [this message]
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=200403292252.i2TMqi222698@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