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

Re: Drupal and PostgreSQL - performance issues?

From: Mikkel Høgh <mikkel(at)hoegh(dot)org>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Subject: Re: Drupal and PostgreSQL - performance issues?
Date: 2008-10-13 08:51:30
Message-ID: BEF0B6B6-8EAB-4082-B81C-819FA0982C0B@hoegh.org (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-performance
Well, in that benchmark, what you say is only true for the Niagara  
processors. On the Opteron page, MySQL performance only drops slightly  
as concurrency passes 50.

MySQL might have a problem with Niagara, but it doesn't seem like it  
has the severe concurrency vulnerability you speak of.

There are many reasons to pick PostgreSQL, but this one doesn't seem  
to be a general thing. In general, MySQL seems to have problems with  
some kinds of threading, since their perfomance on Mac OS X is crappy  
as well for that reason.
--
Kind regards,

Mikkel Høgh <mikkel(at)hoegh(dot)org>

On 13/10/2008, at 10.43, Greg Smith wrote:

> On Sun, 12 Oct 2008, Scott Marlowe wrote:
>
>> It may well be that in a more realistic testing that mysql keeps up  
>> through 5 or 10 client connections then collapses at 40 or 50,  
>> while pgsql keeps climbing in performance.
>
> One of the best pro-PostgreSQL comparisons showing this behavior is  
> at http://tweakers.net/reviews/649/7 MySQL owns that benchmark until  
> you hit 40 users, then...ouch.
>
> --
> * Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com  
> Baltimore, MD

In response to

Responses

pgsql-performance by date

Next:From: Greg SmithDate: 2008-10-13 10:17:31
Subject: Re: Drupal and PostgreSQL - performance issues?
Previous:From: Greg SmithDate: 2008-10-13 08:43:10
Subject: Re: Drupal and PostgreSQL - performance issues?

pgsql-general by date

Next:From: adminDate: 2008-10-13 09:08:24
Subject: Re: Drupal and PostgreSQL - performance issues?
Previous:From: Greg SmithDate: 2008-10-13 08:43:10
Subject: Re: Drupal and PostgreSQL - performance issues?

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