pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jignesh K. Shah <J.K.Shah@Sun.COM>
To: decibel <decibel@decibel.org>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Proposal of tunable fix for scalability of 8.4
Date: Sun, 15 Mar 2009 16:42:40 -0400
Message-ID: <49BD6840.4000403@sun.com> (raw)
In-Reply-To: <D4B5954C-4E01-40B7-BC6E-F98842593889@decibel.org>
References: <C5DEE151.33BA%scott@richrelevance.com>
	<49BA53CF.4020702@sun.com>
	<49BA742D.3050203@sun.com>
	<49BA8CF6.6090604@sun.com>
	<49BABBCE.8090501@sun.com>
	<D4B5954C-4E01-40B7-BC6E-F98842593889@decibel.org>



decibel wrote:
> On Mar 13, 2009, at 3:02 PM, Jignesh K. Shah wrote:
>> vmstat seems similar to wakeup some
>> kthr      memory            page            disk          faults      
>> cpu
>> r b w   swap  free  re  mf pi po fr de sr s0 s1 s2 sd   in   sy   cs 
>> us sy id
>> 63 0 0 45535728 38689856 0 14 0 0 0  0  0  0  0  0  0 163318 334225 
>> 360179 47 17 36
>> 85 0 0 45436736 38690760 0 6 0 0  0  0  0  0  0  0  0 165536 347462 
>> 365987 47 17 36
>> 59 0 0 45405184 38681752 0 11 0 0 0  0  0  0  0  0  0 155153 326182 
>> 345527 47 16 37
>> 53 0 0 45393816 38673344 0 6 0 0  0  0  0  0  0  0  0 152752 317851 
>> 340737 47 16 37
>> 66 0 0 45378312 38651920 0 11 0 0 0  0  0  0  0  0  0 150979 304350 
>> 336915 47 16 38
>> 67 0 0 45489520 38639664 0 5 0 0  0  0  0  0  0  0  0 157188 318958 
>> 351905 47 16 37
>> 82 0 0 45483600 38633344 0 10 0 0 0  0  0  0  0  0  0 168797 348619 
>> 375827 47 17 36
>> 68 0 0 45463008 38614432 0 9 0 0  0  0  0  0  0  0  0 173020 376594 
>> 385370 47 18 35
>> 54 0 0 45451376 38603792 0 13 0 0 0  0  0  0  0  0  0 161891 342522 
>> 364286 48 17 35
>> 41 0 0 45356544 38605976 0 5 0 0  0  0  0  0  0  0  0 167250 358320 
>> 372469 47 17 36
>> 27 0 0 45323472 38596952 0 11 0 0 0  0  0  0  0  0  0 165099 344695 
>> 364256 48 17 35
>
>
> The good news is there's now at least enough runnable procs. What I 
> find *extremely* odd is the CPU usage is almost dead constant...
Generally when there is dead constant.. signs of classic bottleneck ;-)  
We will be fixing one to get to another.. but knocking bottlenecks is 
the name of the game I think

-Jignesh

-- 
Jignesh Shah           http://blogs.sun.com/jkshah  			
The New Sun Microsystems,Inc   http://sun.com/postgresql




view thread (119+ messages)  latest in thread

Message-ID: <49BD6840.4000403@sun.com>
Permalink:  ../49BD6840.4000403@sun.com/
Also on:    postgresql.org/message-id/49BD6840.4000403@sun.com

 · 

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: J.K.Shah@Sun.COM, decibel@decibel.org
  Subject: Re: Proposal of tunable fix for scalability of 8.4
  In-Reply-To: <49BD6840.4000403@sun.com>

* 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