| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: What exactly is our CRC algorithm? |
| Date: | 2014-11-19 16:49:40 |
| Message-ID: | CA+TgmoZ4ct6KYg-ofw8tC6fudYNabwMOD=WN2Q6ZcgCoJVsJPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 19, 2014 at 11:44 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> That's an interesting choice of workload. That sure is heavy on the CRC
> calculation, but the speed of pg_xlogdump hardly matters in real life.
But isn't a workload that is heavy on CRC calculation exactly what we
want here? That way we can see clearly how much benefit we're getting
on that particular part of the computation. It'll still speed up
other workloads, too, just not as much.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-11-19 17:01:14 | Re: proposal: plpgsql - Assert statement |
| Previous Message | Heikki Linnakangas | 2014-11-19 16:44:33 | Re: What exactly is our CRC algorithm? |