From: Daniel van Ham Colchete <daniel.colchete@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: New to PostgreSQL, performance considerations
Date: Mon, 11 Dec 2006 18:07:26 -0200
Message-ID: <8a0c7af10612111207u9f3763dg4eb381b37bd98304@mail.gmail.com> (raw)
In-Reply-To: <20061211140256.GA25975@uio.no>
References: <8a0c7af10612101141n2c7727c3r2f92345753960808@mail.gmail.com>
<430d92a20612101336r3de8862coe618277fccb4006a@mail.gmail.com>
<8a0c7af10612101702i49b5a533v4a2300d90d9dae6b@mail.gmail.com>
<20061211021847.GE16692@mathom.us>
<8a0c7af10612110305u305124b2v3d63491b5f57a86b@mail.gmail.com>
<20061211121547.GF16692@mathom.us>
<8a0c7af10612110517v26025645i3d191b9e7e5ab742@mail.gmail.com>
<20061211140256.GA25975@uio.no>
On 12/11/06, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
> On Mon, Dec 11, 2006 at 11:17:06AM -0200, Daniel van Ham Colchete wrote:
> > I just remebered one case with MySQL. When I changed the distro from
> > Conectiva 10 (rpm-based ended brazilian distro) to Gentoo, a MySQL
> > operation that usually took 2 minutes to run, ended in 47 seconds.
>
> How do you know that this improvement had _anything_ to do with the use of
> different optimization flags? Were even the MySQL versions or configuration
> the same?
>
> > This is absolutely vage.
>
> Indeed it is.
Finally we agreed on something.
>
> > I don't have how to prove it to you.
>
> No, but you should stop making this sort of "absolutely essential" claims if
> you can't.
>
> > And I can't mesure how each factor helped: compiling glibc and Mysql with
> > good cflags, rebuilding my database in a ordered way, never kernel, etc..
>
> Exactly. So why are you attributing it to the first factor only? And why do
> you think this would carry over to PostgreSQL?
>
> Remember, anecdotal evidence isn't.
But that's exactly what I said. I'm not attributing this case to the
optimization factor. As I said there are a lot of factors involved.
The MySQL version change of a minor upgrade (from 4.1.15 to 4.1.21).
Steinar, I say I'll do the benchmark and it will be the end of the story.
>
> /* Steinar */
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: daniel.colchete@gmail.com
Subject: Re: New to PostgreSQL, performance considerations
In-Reply-To: <8a0c7af10612111207u9f3763dg4eb381b37bd98304@mail.gmail.com>
References: <8a0c7af10612101141n2c7727c3r2f92345753960808@mail.gmail.com> <430d92a20612101336r3de8862coe618277fccb4006a@mail.gmail.com> <8a0c7af10612101702i49b5a533v4a2300d90d9dae6b@mail.gmail.com> <20061211021847.GE16692@mathom.us> <8a0c7af10612110305u305124b2v3d63491b5f57a86b@mail.gmail.com> <20061211121547.GF16692@mathom.us> <8a0c7af10612110517v26025645i3d191b9e7e5ab742@mail.gmail.com> <20061211140256.GA25975@uio.no> <8a0c7af10612111207u9f3763dg4eb381b37bd98304@mail.gmail.com>
* 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