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

Re: scale up (postgresql vs mssql)

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Eyal Wilde <eyal(at)impactsoft(dot)co(dot)il>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: scale up (postgresql vs mssql)
Date: 2012-04-13 15:04:39
Message-ID: CAGTBQpYga9Uo4n=qUPyYOkuzW+2MoDYoRnBF53jvb546=Hbbqg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Wed, Apr 11, 2012 at 7:11 PM, Eyal Wilde <eyal(at)impactsoft(dot)co(dot)il> wrote:
> in a single execution postgresql may be less the twice slower than ms-sql,
> but in 20 simultaneous clients, it's about 6 times worse. why is that?
>
> the hardware is one 4-core xeon. 8GB of ram. the database size is just a few
> GB's. centos-6.2.
>
> do you think the fact that postgresql use a process per connection (instead
> of multi-threading) is inherently a weakness of postgrsql, regarding
> scale-up?
> would it be better to limit the number of connections to something like 4,
> so that executions don't interrupt each other?

What about posting some details on the tables, the 20 queries, the temp table?

I'm thinking creating so many temp tables may be hurting pgsql more
than mssql. You might want to try unlogged temp tables, which more
closely resemble mssql temp tables.

In response to

Responses

pgsql-performance by date

Next:From: xlashDate: 2012-04-13 16:14:47
Subject: PostgreSQL - Help Optimizing performance - full text search on Heroku
Previous:From: Kevin GrittnerDate: 2012-04-13 14:40:01
Subject: Re: scale up (postgresql vs mssql)

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