pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Josh Berkus <josh@agliodbs.com>
To: pgsql-hackers@postgresql.org, Jignesh Shah <jkshah@gmail.com>
Subject: Re: patch: improve SLRU replacement algorithm
Date: Wed, 04 Apr 2012 16:06:54 -0700
Message-ID: <4F7CD40E.10401@agliodbs.com> (raw)
In-Reply-To: <11561.1333580573@sss.pgh.pa.us>
References: <CA+TgmoZ6cWexkRa4v3nUykZebzJkrkCoS_EDt6uDuP7RTPq7Bg@mail.gmail.com>
<CAM-w4HM76yi=Y-5Qtw_0iV5SeAVeGbA_XGL1dKC9Xoo1R1exQw@mail.gmail.com>
<CA+TgmoYNucX7kWNwE5EVFEabV6KQXgtvz_5ba=mU2trwpDRyig@mail.gmail.com>
<CA+U5nM+3qXwfJaRdRyFXWvvF4t151-BJY5cq5jWgGOSFdeviRg@mail.gmail.com>
<CAM-w4HN_e96YCufGP3z3mkCGJOkp0OAyVUM75jK=YLxJo8L7_g@mail.gmail.com>
<11561.1333580573@sss.pgh.pa.us>
On 4/4/12 4:02 PM, Tom Lane wrote:
> Greg Stark <stark@mit.edu> writes:
>> On Wed, Apr 4, 2012 at 9:34 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>> Why is this pgbench run accessing so much unhinted data that is > 1
>>> million transactions old? Do you believe those numbers? Looks weird.
>
>> I think this is in the nature of the workload pgbench does. Because
>> the updates are uniformly distributed, not concentrated 90% in 10% of
>> the buffers like most real-world systems, (and I believe pgbench only
>> does index lookups) the second time a tuple is looked at is going to
>> average N/2 transactions later where N is the number of tuples.
>
> That's a good point, and it makes me wonder whether pgbench is the right
> test case to be micro-optimizing around. It would be a good idea to at
> least compare the numbers for something with more locality of reference.
Jignesh, would DVDstore help for this?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
view thread (30+ messages) latest in thread
Message-ID: <4F7CD40E.10401@agliodbs.com>
Permalink: ../4F7CD40E.10401@agliodbs.com/
Also on: postgresql.org/message-id/4F7CD40E.10401@agliodbs.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: josh@agliodbs.com, jkshah@gmail.com
Subject: Re: patch: improve SLRU replacement algorithm
In-Reply-To: <4F7CD40E.10401@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox