From: Jignesh K. Shah <J.K.Shah@Sun.COM>
To: Scott Carey <scott@richrelevance.com>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Proposal of tunable fix for scalability of 8.4
Date: Wed, 18 Mar 2009 17:57:25 -0400
Message-ID: <49C16E45.9020307@sun.com> (raw)
In-Reply-To: <C5E6B2A1.37BF%scott@richrelevance.com>
References: <C5E6B2A1.37BF%scott@richrelevance.com>
On 03/18/09 17:16, Scott Carey wrote:
> On 3/18/09 4:36 AM, "Gregory Stark" <stark@enterprisedb.com> wrote:
>
>
>> "Jignesh K. Shah" <J.K.Shah@Sun.COM> writes:
>>
>>
>>> In next couple of weeks I plan to test the patch on a different x64 based
>>> system to do a sanity testing on lower number of cores and also try out other
>>> workloads ...
>>>
>> I'm actually more interested in the large number of cores but fewer processes
>> and lower max_connections. If you set max_connections to 64 and eliminate the
>> wait time you should, in theory, be able to get 100% cpu usage. It would be
>> very interesting to track down the contention which is preventing that.
>>
>
> My previous calculation in this thread showed that even at 0 wait time, the
> client seems to introduce ~3ms wait time overhead on average. So it takes
> close to 128 threads in each test to stop the linear scaling since the
> average processing time seems to be about ~3ms.
> Either that, or the tests actually are running on a system capable of 128
> threads.
>
>
Nope 64 threads for sure .. Verified it number of times ..
-Jignesh
>> --
>> Gregory Stark
>> EnterpriseDB http://www.enterprisedb.com
>> Ask me about EnterpriseDB's PostGIS support!
>>
>> -
>> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-performance
>>
>>
>
>
> -
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
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, scott@richrelevance.com, stark@enterprisedb.com, simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov
Subject: Re: Proposal of tunable fix for scalability of 8.4
In-Reply-To: <49C16E45.9020307@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