From: Arjen van der Meijden <acmmailing@tweakers.net>
To: PFC <lists@peufeu.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres Benchmark Results
Date: Sun, 20 May 2007 19:26:38 +0200
Message-ID: <465084CE.5010703@tweakers.net> (raw)
In-Reply-To: <op.tsmxycgdcigqcu@apollo13>
References: <op.tsmrv71ecigqcu@apollo13>
<46507A40.505@tweakers.net>
<op.tsmxycgdcigqcu@apollo13>
On 20-5-2007 19:09 PFC wrote:
> Since I use lighttpd, I don't really care about the number of actual
> slow clients (ie. real concurrent HTTP connections). Everything is
> funneled through those 8 PHP processes, so postgres never sees huge
> concurrency.
Well, that would only be in favour of postgres anyway, it scales in our
benchmarks better to multiple cpu's, multiple clients and appaerantly in
yours to larger datasets. MySQL seems to be faster up untill a certain
amount of concurrent clients (close to the amount of cpu's available)
and beyond that can collapse dramatically.
> I'm writing a full report, but I'm having a lot of problems with
> MySQL, I'd like to give it a fair chance, but it shows real obstination
> in NOT working.
Yeah, it displayed very odd behaviour when doing benchmarks here too. If
you haven't done already, you can try the newest 5.0-verion (5.0.41?)
which eliminates several scaling issues in InnoDB, but afaik not all of
them. Besides that, it just can be pretty painful to get a certain query
fast, although we've not very often seen it failing completely in the
last few years.
Best regards,
Arjen van der Meijden
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: acmmailing@tweakers.net, lists@peufeu.com
Subject: Re: Postgres Benchmark Results
In-Reply-To: <465084CE.5010703@tweakers.net>
* 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