From: Michael Stone <mstone+postgres@mathom.us>
To: pgsql-performance@postgresql.org
Subject: Re: New to PostgreSQL, performance considerations
Date: Mon, 11 Dec 2006 12:31:08 -0500
Message-ID: <20061211173105.GH16692@mathom.us> (raw)
In-Reply-To: <E1GtolA-0008Fk-4R@elasmtp-banded.atl.sa.earthlink.net>
References: <8a0c7af10612101141n2c7727c3r2f92345753960808@mail.gmail.com>
<430d92a20612101336r3de8862coe618277fccb4006a@mail.gmail.com>
<8a0c7af10612101702i49b5a533v4a2300d90d9dae6b@mail.gmail.com>
<20061211021847.GE16692@mathom.us>
<8a0c7af10612110305u305124b2v3d63491b5f57a86b@mail.gmail.com>
<87u002mv49.fsf@wolfe.cbbrowne.com>
<8a0c7af10612110531sbb019ck259fb16d131fdb50@mail.gmail.com>
<60psaq5t94.fsf@dba2.int.libertyrms.com>
<E1GtolA-0008Fk-4R@elasmtp-banded.atl.sa.earthlink.net>
On Mon, Dec 11, 2006 at 12:15:51PM -0500, Ron wrote:
>I'd say the fairest attitude is to do everything we can to support
>having the proper experiments done w/o presuming the results.
Who's presuming results?[1] It is fair to say that making extraordinary
claims without any evidence should be discouraged. It's also fair to say
that if there are specific things that need cpu-specific tuning they'll
be fairly limited critical areas (e.g., locks) which would probably be
better implemented with a hand-tuned code and runtime cpu detection than
by magical mystical compiler invocations.
Mike Stone
[1] I will say that I have never seen a realistic benchmark of general
code where the compiler flags made a statistically significant
difference in the runtime. There are some particularly cpu-intensive
codes, like some science simulations or encoding routines where they
matter, but that's not the norm--and many of those algorithms already
have hand-tuned versions which will outperform autogenerated code. You'd
think that with all the talk that the users of certain OS's generate
about CFLAG settings, there'd be some well-published numbers backing up
the hype. At any rate if there were numbers to back the claim then I
think they could certainly be considered without prejudice.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mstone+postgres@mathom.us
Subject: Re: New to PostgreSQL, performance considerations
In-Reply-To: <20061211173105.GH16692@mathom.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox