Re: parametric block size?

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parametric block size?
Date: 2014-07-26 17:37:51
Message-ID: alpine.DEB.2.10.1407261925170.13352@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> The basic claim that I'm making wrt to this benchmark is that there may
>> be a significant impact on performance with changing the block size,
>> thus this is worth investigating. I think this claim is quite safe,
>> even if the benchmark is not the best possible.
>
> Well, you went straight to making it something adjustable at run time.

What I really did was to go straight to asking the question:-)

Up to now I have two answers, or really caveats:

- a varying blocksize implementation should have minimum effects
on performance for user of the default settings.

- the said benchmark may not be that meaningful, so the performance
impact is to be accessed more thoroughly.

> And I don't see that as being warranted at this point. But further
> benchmarks sound like a good idea.

Yep. A 10% potential performance impact looks worth the investigation.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-07-26 17:58:38 Re: [RFC] Should smgrtruncate() avoid sending sinval message for temp relations
Previous Message Andres Freund 2014-07-26 17:17:59 Re: parametric block size?