pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: Dave Page <dpage@vale-housing.co.uk>
Cc: pgsql-performance@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <mha@sollentuna.net>
Cc: Win 32 hackers PGSQL <pgsql-hackers-win32@postgresql.org>
Subject: Re: [PERFORM] scalability issues on win32
Date: Thu, 2 Dec 2004 14:28:17 -0500 (EST)
Message-ID: <200412021928.iB2JSHo09487@candle.pha.pa.us> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A754F@Herge.rcsinc.local>

Merlin Moncure wrote:
> > > This was an intersting Win32/linux comparison. I expected
> > > Linux to scale better, but I was surprised how poorly XP
> > > scaled.  It reinforces our perception that Win32 is for low
> > > traffic servers.
> > 
> > That's a bit harsh given the lack of any further investigation so far
> > isn't it? Win32 can run perfectly well with other DBMSs with hundreds
> of
> > users.
> > 
> > Any chance you can profile your test runs Merlin?
> > 
> 
> Ok, I am starting to strongly suspect the statistics collector of
> various kinds of malfeasance.  Right now I am running with the stats
> collector off and I am getting much better scalability and much more
> deterministic query times...that is, even when under moderate to heavy
> load query running times are proportional to the number of users on the
> system...the system is purring like a kitten right now with over a 100
> users logged in.
> 
> This coupled with the fact that I was getting random restarts with the
> collector process makes me think that there is some kind of issue with
> the ipc between the collector and the backends that is blocking and/or
> is being improperly handled after failure.
> 
> I was running with statement level stats on under scenarios with
> extremely high levels of query activity where the server might be
> processing 500-1500 queries/second or more spread out over multiple
> backends.
> 
> I'll look into this issue more over next several days.  I'll dip back
> into the code and see if I can come up with a better
> answer...unfortunately I can't run the stats collector on until I can
> schedule another load test.

OK, the big problem is that we are nearing RC1.  We would like some
feedback on this as soon as possible.  A major Win32 cleanup for this
could delay the 8.0 release.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (14+ messages)  latest in thread

Message-ID: <200412021928.iB2JSHo09487@candle.pha.pa.us>
Permalink:  ../200412021928.iB2JSHo09487@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200412021928.iB2JSHo09487@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, merlin.moncure@rcsonline.com, dpage@vale-housing.co.uk, tgl@sss.pgh.pa.us, mha@sollentuna.net, pgsql-hackers-win32@postgresql.org
  Subject: Re: [PERFORM] scalability issues on win32
  In-Reply-To: <200412021928.iB2JSHo09487@candle.pha.pa.us>

* 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