From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: limiting hint bit I/O |
Date: | 2011-01-14 18:06:25 |
Message-ID: | AANLkTikwMNviCJpx4cRtX5593G2PZy-Ms8QLXB9H=RGf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 14, 2011 at 1:02 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> this seems to be speeding up the first run by 6x at the expense of
>> slowing down many subsequent runs by 10-15%.
>
> If the overall throughput when measured far enough out to have hit a
> steady state again is anywhere in the neighborhood of the unpatched
> throughput, the leveling of the response times has enough value to
> merit the change. At least in my world.
I think it would eventually settle down to the same speed, but it
might take a really long time. I got impatient before I got that far.
I'm hoping some will pick it up and play with it some more (hint,
hint).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-01-14 18:07:55 | Re: limiting hint bit I/O |
Previous Message | Tom Lane | 2011-01-14 18:06:03 | Re: limiting hint bit I/O |