pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe <svn@freedomcircle.net>
To: Magnus Hagander <mha@sollentuna.net>
Cc: Gavin Sherry <swm@alcove.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Comparative performance
Date: Thu, 29 Sep 2005 08:16:11 -0400
Message-ID: <433BDB0B.8010002@freedomcircle.net> (raw)
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE92E6D6@algol.sollentuna.se>
References: <6BCB9D8A16AC4241919521715F4D8BCE92E6D6@algol.sollentuna.se>

Magnus Hagander wrote:
> That actually depends a lot on *how* you use it. I've seen pg-on-windows
> deployments that come within a few percent of the linux performance.
> I've also seen those that are absolutely horrible compared.
> 
> One sure way to kill the performance is to do a lot of small
> connections. Using persistent connection is even more important on
> Windows than it is on Unix. It could easily explain a difference like
> this.

I just tried using pg_pconnect() and I didn't notice any significant 
improvement.  What bothers me most is that with Postgres I tend to see jerky 
behavior on almost every page:  the upper 1/2 or 2/3 of the page is displayed 
first and you can see a blank bottom (or you can see a half-filled completion 
bar).  With MySQL each page is generally displayed in one swoop.

Joe




view thread (25+ messages)  latest in thread

Message-ID: <433BDB0B.8010002@freedomcircle.net>
Permalink:  ../433BDB0B.8010002@freedomcircle.net/
Also on:    postgresql.org/message-id/433BDB0B.8010002@freedomcircle.net

 · 

reply

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: svn@freedomcircle.net, mha@sollentuna.net, swm@alcove.com.au
  Subject: Re: Comparative performance
  In-Reply-To: <433BDB0B.8010002@freedomcircle.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