From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
Cc: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: What exactly is our CRC algorithm? |
Date: | 2014-11-26 23:56:52 |
Message-ID: | 20141126235652.GA22659@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 21, 2014 at 07:49:45AM -0600, ktm(at)rice(dot)edu wrote:
> Hi,
>
> This indicates that another part of the system is the resource limit,
> not the CRC calculation. My money is on the I/O system. Try it using
> an in memory filesystem and see if that matters. Even if it is still
> the same results, at least the new version of CRC is no worse than
> the current version.
I would test it with fsync=off to remove the fsync delay. That will
simulate an SSD or BBU controller.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2014-11-27 00:13:41 | Re: 9.2 recovery/startup problems |
Previous Message | Michael Paquier | 2014-11-26 23:47:59 | Re: 9.2 recovery/startup problems |