Re: survey of WAL blocksize changes - Mailing list pgsql-hackers

From Mark Wong
Subject Re: survey of WAL blocksize changes
Date
Msg-id 70c01d1d0905271751x31ee6e15k7b8a8aff852fcb64@mail.gmail.com
Whole thread Raw
In response to Re: survey of WAL blocksize changes  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: survey of WAL blocksize changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: survey of WAL blocksize changes  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Wed, May 27, 2009 at 1:46 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>
> On Tue, 2009-05-26 at 19:51 -0700, Mark Wong wrote:
>> It appears for this workload using a 16KB or 32KB gets more than 4%
>> throughput improvement, but some of that could be noise.
>
> The baseline appears to have a significant jump in txn response time
> after 77 mins on the baseline test. I think you should rerun that. My
> guess would be it will reduce any gains shown with higher settings.

Oopsies.  I've rerun, but now that there is no dip, the average
throughput still didn't change much:

BS notpm % Change from default
-- ----- ----------1 14673 -5.1%2 15864 2.7%4 15774 2.1%8 15454 (default)
16 16118 4.3%
32 16051 3.9%
64 14874 -3.8%

Pointers to raw data:

BS url
-- ---1 http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.1/2
http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.2/4
http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.4/8
http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.8/report/
16 http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.16/
32 http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.32/
64 http://207.173.203.223/~markwkm/community6/dbt2/m1500-8.4beta2/m1500.8.4beta2.wal.64/


Regards,
Mark Wong


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: User-facing aspects of serializable transactions
Next
From: Tom Lane
Date:
Subject: Re: User-facing aspects of serializable transactions