Re: Enabling Checksums

From: Ants Aasma <ants(at)cybertec(dot)at>
To: Ants Aasma <ants(at)cybertec(dot)at>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Enabling Checksums
Date: 2013-04-09 07:39:35
Message-ID: CA+CSw_ugiW91Qeg+7k=PDvtxbo+Q95D4eufPsNutvQHKHyr2UQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 9, 2013 at 5:35 AM, Ants Aasma <ants(at)cybertec(dot)at> wrote:
> Quick bench results on the worst case workload:
> master no checksums: tps = 15.561848
> master with checksums: tps = 1.695450
> simd checksums: tps = 14.602698

For reference, results for the generic version, with default build
params and with the ones required for vectorizing:
simd checksums generic: tps = 6.683347
simd checksums generic vectorized: tps = 12.755203

It would be great if we could hint other platforms about the
vectorization possibilities. Unfortunately I'm not strong enough in
portability fu to come up with the necessary incantations to make all
compilers dance to my will.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2013-04-09 07:42:29 Re: Inconsistent DB data in Streaming Replication
Previous Message Jeff Davis 2013-04-09 07:37:43 Re: corrupt pages detected by enabling checksums