Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL and sql-bench

From: Arjen van der Meijden <acmmailing(at)tweakers(dot)net>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, yoav x <yoav112003(at)yahoo(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL and sql-bench
Date: 2006-09-21 22:26:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On 21-9-2006 23:49 Jim C. Nasby wrote:
> Even with fsync = off, there's still a non-trivial amount of overhead
> brought on by MVCC that's missing in myisam. If you don't care about
> concurrency or ACIDity, but performance is critical (the case that the
> MySQL benchmark favors), then PostgreSQL probably isn't for you.

That depends on the required scalability (both in number of cpu's and in 
number of concurrent clients). In our benchmarks MySQL is beaten by 
PostgreSQL in a read-mostly environment with queries that are designed 
for MySQL, but slightly adjusted to work on PostgreSQL (for MySQL 5.0 
and 5.1, about the same adjustments where needed).
But for very low amounts of concurrent users, MySQL outperforms PostgreSQL.

Have a look here:
and here:

As you can see both MySQL 5.0 and 4.1 start much higher for a few 
clients, but when you add more clients or more cpu's, MySQL scales less 
good and even starts dropping performance and soon is far behind 
compared to PostgreSQL.

So for a web-application, PostgreSQL may be much better, since generally 
the only situation where you need maximum performance, is when you have 
to service a lot of concurrent visitors.
But if you benchmark only with a single thread or do benchmarks that are 
no where near a real-life environment, it may show very different 
results of course.

Best regards,

Arjen van der Meijden

In response to

pgsql-performance by date

Next:From: Luke LonerganDate: 2006-09-21 23:31:49
Subject: Re: Large tables (was: RAID 0 not as fast as
Previous:From: Jim C. NasbyDate: 2006-09-21 21:49:14
Subject: Re: PostgreSQL and sql-bench

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group