From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Ants Aasma <ants(at)cybertec(dot)at>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WAL CPU overhead/optimization (was Master-slave visibility order) |
Date: | 2013-09-03 21:25:01 |
Message-ID: | 522653AD.7000804@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/03/2013 05:27 PM, Robert Haas wrote:
> On Thu, Aug 29, 2013 at 8:22 PM, Ants Aasma <ants(at)cybertec(dot)at> wrote:
>> I might give it a shot later this cycle as I have familiarized my self
>> with the problem domain anyway. I understand the appeal of staying
>> with what we have, but this would cap the speedup at 4x and has large
>> caveats with the extra lookup tables. A 28x speedup might be worth the
>> extra effort.
> I agree. However, on the flip side, a bird in the hand is worth two
> in the bush. A patch that just does the same thing faster is likely
> to be less controversial than changing the algorithm, and does not
> preclude changing the algorithm later.
>
Has anybody looked at the recent i5/i7 added hrdware support for CRC32 ?
http://www.strchr.com/crc32_popcnt
From number there it is probably still slower than xxhash, but it might
be worth doing as
an interim optimisation.
Cheers
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-09-03 22:41:27 | Re: Backup throttling |
Previous Message | Antonin Houska | 2013-09-03 21:12:40 | Re: Backup throttling |