| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Subject: | Re: Avoiding repeated snapshot computation |
| Date: | 2011-11-26 22:39:23 |
| Message-ID: | CA+Tgmoae8yoVAOVM7PGO5FhLMhN2LL3K3A0iz+4vWuZGWdFisA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 26, 2011 at 5:28 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On Saturday, November 26, 2011 09:52:17 PM Tom Lane wrote:
>> I'd just as soon keep the fields in a logical order.
> Btw, I don't think the new order is necessarily worse than the old one.
You forget to attach the benchmark results.
My impression is that cache lines on modern hardware are 64 or 128
*bytes*, in which case this wouldn't matter a bit.
But testing is even better than guessing.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-11-26 22:49:19 | Re: Avoiding repeated snapshot computation |
| Previous Message | Andres Freund | 2011-11-26 22:28:30 | Re: Avoiding repeated snapshot computation |