From: | pgsql-performance(at)sysd(dot)com |
---|---|
To: | Jeff <threshar(at)torgo(dot)978(dot)org> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Sun performance - Major discovery! |
Date: | 2003-10-08 19:22:08 |
Message-ID: | 200310081922.h98JM9LW029751@startide.sysdetect.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
In message <Pine(dot)BSF(dot)4(dot)44(dot)0310081408370(dot)64781-100000(at)torgo(dot)978(dot)org>, Jeff writes:
I'll go run the regression test suite with my gcc -O2 pg and the suncc pg.
See if they pass the test.
My default set of gcc optimization flags is:
-O3 -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions -mcpu=i686 -march=i686
Obviously the last two flags product CPU specific code, so would have
to differ...autoconf is always possible, but so is just lopping them off.
I have found these flags to produce faster code that a simple -O2, but
I understand the exact combination which is best for you is
code-dependent. Of course, if you are getting really excited, you can
use -fbranch-probabilities, but as you will see if you investigate
that requires some profiling information, so is not very easy to
actually practically use.
-Seth Robertson
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-10-08 19:26:08 | Re: Postgresql 7.3.4 compile failes on NetBSD 1.6 mac68k |
Previous Message | Andrew Dunstan | 2003-10-08 18:50:24 | Re: [PERFORM] Sun performance - Major discovery! |
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Hihn | 2003-10-08 19:24:56 | Re: Compare rows |
Previous Message | Greg Spiegelberg | 2003-10-08 19:10:53 | Re: Compare rows |