Sv: Re: Sv: Re: Sv: Re: data-checksums - Mailing list pgsql-general

From Andreas Joseph Krogh
Subject Sv: Re: Sv: Re: Sv: Re: data-checksums
Date
Msg-id VisenaEmail.10b.626308204f206345.160dd34d1f5@tc7-visena
Whole thread Raw
In response to Re: Sv: Re: Sv: Re: data-checksums  (Rob Sargent <robjsargent@gmail.com>)
Responses Re: Sv: Re: Sv: Re: Sv: Re: data-checksums
List pgsql-general
På tirsdag 09. januar 2018 kl. 23:42:45, skrev Rob Sargent <robjsargent@gmail.com>:

   

On 01/09/2018 03:30 PM, Andreas Joseph Krogh wrote:
På tirsdag 09. januar 2018 kl. 23:06:06, skrev Andres Freund <andres@anarazel.de>:
Hi,

On 2018-01-09 21:47:17 +0100, Andreas Joseph Krogh wrote:
> Does PG use HW-accellerated crc if CPU supports it[1]?

Yes we do, for WAL checksums. The page checksums are a different
algorithm though, one which has the advantage of being SIMD compatible.

The checksum computations have some impact, but if there's bigger impact
it's much more likely to be related to the fact that some hint bit
writes to a page now needs to be WAL logged.
 
But SIMD-instructions are also HW-accellerated by modern CPUs IIUC?
 
So, if these CRCs all are HW-accelerated the penalty chould be next to neglishable?
 
Leading directly back to JD's proposed documentation update.
 
Ducumentation mentioning "Depends on hardware" and "you should test" isn't really helpfull imo. as it is too general and can be said about just about anything.
 
Being explicit about usage of HW-accelerated (in CPU) instructions in algorithms used is helpfull, and might help users choose enabling data-checksums.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
 
Attachment

pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Sv: Re: Sv: Re: data-checksums
Next
From: Andres Freund
Date:
Subject: Re: Sv: Re: Sv: Re: Sv: Re: data-checksums