pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Jignesh K. Shah <J.K.Shah@Sun.COM>
Cc: pgsql-performance@postgresql.org
Subject: Re: Proposal of tunable fix for scalability of 8.4
Date: Thu, 12 Mar 2009 09:07:39 -0500
Message-ID: <49B8D0DB.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <49B85CAC.70807@sun.com>
References: <49B824DD.7090302@sun.com>
	<49B7F470.EE98.0025.0@wicourts.gov>
	<49B85CAC.70807@sun.com>

"Jignesh K. Shah" <J.K.Shah@Sun.COM> wrote: 
> On 03/11/09 18:27, Kevin Grittner wrote:
>> "Jignesh K. Shah" <J.K.Shah@Sun.COM> wrote: 
 
>>> Rerunning similar tests on a 64-thread UltraSPARC T2plus based
>>> server config
>>   
>>> (IO is not a problem... all in RAM .. no disks):
>>> Time:Users:Type:TPM: Response Time
>>> 60: 100: Medium Throughput: 10552.000 Avg Medium Resp: 0.006
>>> 120: 200: Medium Throughput: 22897.000 Avg Medium Resp: 0.006
>>> 180: 300: Medium Throughput: 33099.000 Avg Medium Resp: 0.009
>>> 240: 400: Medium Throughput: 44692.000 Avg Medium Resp: 0.007
>>> 300: 500: Medium Throughput: 56455.000 Avg Medium Resp: 0.007
>>> 360: 600: Medium Throughput: 67220.000 Avg Medium Resp: 0.008
>>> 420: 700: Medium Throughput: 77592.000 Avg Medium Resp: 0.009
 
>> I'm a lot more interested in what's happening between 60 and 180
than
>> over 1000, personally.  If there was a RAID involved, I'd put it
down
>> to better use of the numerous spindles, but when it's all in RAM it
>> makes no sense.
 
> The problem is the CPUs are not all busy there is plenty of idle
cycles 
> since PostgreSQL ends up in situations where they are all waiting for

> lockacquires for exclusive..
 
Precisely.  This is the area where it seems there is the most to gain.
The area you're looking at seems to have less than a 2X gain
available.
This part of the curve clearly has much more.
 
-Kevin



view thread (119+ messages)  latest in thread

Message-ID: <49B8D0DB.EE98.0025.0@wicourts.gov>
Permalink:  ../49B8D0DB.EE98.0025.0@wicourts.gov/
Also on:    postgresql.org/message-id/49B8D0DB.EE98.0025.0@wicourts.gov

 · 

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: Kevin.Grittner@wicourts.gov, J.K.Shah@Sun.COM
  Subject: Re: Proposal of tunable fix for scalability of 8.4
  In-Reply-To: <49B8D0DB.EE98.0025.0@wicourts.gov>

* 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