From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How much do the hint bits help? |
Date: | 2010-12-22 16:12:04 |
Message-ID: | AANLkTi=u5fT8NuZnWpnAEB6aOdZO7+Okj=mPBju-v=KT@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 22, 2010 at 11:06 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> well, simon's point that hint bits complicate checksum may nor may not
>> be the case, but no hint bits = less i/o = less checksumming (unless
>> you checksum around the hint bits).
>
> I think you're optimistically assuming the extra clog accesses don't
> cost any I/O.
right, but clog is much more highly packed which is both a good and a
bad thing. my conjecture here is that jamming the clog files is
actually good, because that keeps them 'hot' and more than compensates
the extra heap i/o. the extra lock of course is scary.
here's the thing, compared to the 90's when they were put in, the
transaction space has shrunk by half and we put gigabytes, not
megabytes of memory into servers. what does this mean for the clog?
that's what i'm after.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-12-22 16:14:01 | Re: How much do the hint bits help? |
Previous Message | Merlin Moncure | 2010-12-22 16:06:40 | Re: How much do the hint bits help? |