Re: [REVIEW] Re: Compression of full-page-writes - Mailing list pgsql-hackers

From Ants Aasma
Subject Re: [REVIEW] Re: Compression of full-page-writes
Date
Msg-id CA+CSw_vAKMz80WiNUZNt_5XHyqR4YUinfTQO_H+Cnk31W33osQ@mail.gmail.com
Whole thread Raw
In response to Re: [REVIEW] Re: Compression of full-page-writes  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: [REVIEW] Re: Compression of full-page-writes  (Andres Freund <andres@2ndquadrant.com>)
Re: [REVIEW] Re: Compression of full-page-writes  ("ktm@rice.edu" <ktm@rice.edu>)
Re: [REVIEW] Re: Compression of full-page-writes  (Arthur Silva <arthurprs@gmail.com>)
List pgsql-hackers
On Fri, Sep 12, 2014 at 10:38 PM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> I don't mean that we should abandon this patch - compression makes the WAL
> smaller which has all kinds of other benefits, even if it makes the raw TPS
> throughput of the system worse. But I'm just saying that these TPS
> comparisons should be taken with a grain of salt. We probably should
> consider switching to a faster CRC algorithm again, regardless of what we do
> with compression.

CRC is a pretty awfully slow algorithm for checksums. We should
consider switching it out for something more modern. CityHash,
MurmurHash3 and xxhash look like pretty good candidates, being around
an order of magnitude faster than CRC. I'm hoping to investigate
substituting the WAL checksum algorithm 9.5.

Given the room for improvement in this area I think it would make
sense to just short-circuit the CRC calculations for testing this
patch to see if the performance improvement is due to less data being
checksummed.

Regards,
Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Stating the significance of Lehman & Yao in the nbtree README
Next
From: Andres Freund
Date:
Subject: Re: CRC algorithm (was Re: [REVIEW] Re: Compression of full-page-writes)