From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: List pgsql-patches <pgsql-patches@postgresql.org>
Subject: Re: [HACKERS] Hint Bits and Write I/O
Date: Tue, 22 Jul 2008 13:44:33 +0100
Message-ID: <1216730673.3894.308.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <17500.1216672435@sss.pgh.pa.us>
References: <1211916951.4489.232.camel@ebony.site>
<15901.1211931165@sss.pgh.pa.us>
<1213797209.9468.126.camel@ebony.site>
<87hcbfq71p.fsf@oxford.xeocode.com>
<1214578938.3845.423.camel@ebony.site>
<1214865781.3845.525.camel@ebony.site>
<2e78013d0807202306t21ff41a9q53673dc9a48bf859@mail.gmail.com>
<1216670891.3894.34.camel@ebony.2ndQuadrant>
<17500.1216672435@sss.pgh.pa.us>
On Mon, 2008-07-21 at 16:33 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > On Mon, 2008-07-21 at 11:36 +0530, Pavan Deolasee wrote:
> >> I think we should try at least one or two possible optimizations and
> >> get some numbers before we jump and make substantial changes to the
> >> code.
>
> > You know you're suggesting months of tests and further discussion. :-(
>
> I agree with Pavan that we should have something that'd at least serve
> as test scaffolding to verify that the framework patch is sane. The
> test code needn't be anything we'd want to commit.
The test code is/was there, in the sense that the patch was (supposed
to) do exactly what it does now, just with extra code to keep track of
hint counts.
Probably the most important point is not yet covered: we don't keep any
track of which blocks are dirtied solely for hint bits. We need to do
this so we can measure the efficacy of *any* patch that seeks to improve
the current situation.
The best time to do this is in integration phase of release, so will do
it then.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
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-patches@postgresql.org
Cc: simon@2ndquadrant.com, tgl@sss.pgh.pa.us, pavan.deolasee@gmail.com
Subject: Re: [HACKERS] Hint Bits and Write I/O
In-Reply-To: <1216730673.3894.308.camel@ebony.2ndQuadrant>
* 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