From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Subject: | Re: Substituting Checksum Algorithm (was: Enabling Checksums) |
Date: | 2013-04-26 21:53:10 |
Message-ID: | 1367013190.11576.249.camel@sussancws0025 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2013-04-26 at 16:40 -0400, Greg Smith wrote:
> I think I need to do two baselines: master without checksums, and
> master with extra optimizations but still without checksums. It may be
> the case that using better compile time optimizations gives a general
> speedup that's worth considering regardless. The optimizations seem to
> have a very significant impact on the checksum feature, but I'd like to
> quantify how they change the code a little bit before even getting into
> that.
The patch only affects optimization flags used when compiling
checksum.c, so it should have no effect on other areas of the code.
If you want to compile the whole source with those flags, then just do:
CFLAGS="-msse4.1 -funroll-loops -ftree-vectorize" ./configure
Changing the optimization flags for existing code will have a larger
impact and should be considered separately from checksums.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-04-26 22:09:44 | pg_ctl non-idempotent behavior change |
Previous Message | Greg Smith | 2013-04-26 20:40:20 | Re: Substituting Checksum Algorithm (was: Enabling Checksums) |