From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Jim Nasby <jim(at)nasby(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Clock sweep not caching enough B-Tree leaf pages? |
Date: | 2014-04-28 18:49:36 |
Message-ID: | CAM3SWZRiCdRpSy0e_58ke669-ee2KcULSuKZuyFsj=KYWRX-GQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 25, 2014 at 10:45 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> I've now done a non-limited comparative benchmark of master against
> the patch (once again, with usage_count starting at 6, and
> BM_MAX_USAGE_COUNT at 30) with a Gaussian distribution. Once again,
> the distribution threshold used was consistently 5.0, causing the
> patched pgbench to report for each test:
>
> transaction type: Custom query
> scaling factor: 5000
> standard deviation threshold: 5.00000
> access probability of top 20%, 10% and 5% records: 0.68269 0.38293 0.19741
>
> Results are available from:
>
> http://postgres-benchmarks.s3-website-us-east-1.amazonaws.com/3-sec-delay-gauss/
I updated this with various changes in bgwriter configuration. Perhaps
unsurprisingly, disabling the background writer entirely helps for
both master and patched. It is perhaps notable that the largest
difference between two comparable patch + master test runs is seen
when the background writer is disabled entirely, and 32 clients.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-28 18:50:09 | Re: includedir_internal headers are not self-contained |
Previous Message | Robert Haas | 2014-04-28 18:44:16 | Re: includedir_internal headers are not self-contained |