Message-ID: <49CFE92A.8000101@agliodbs.com>
Date: Sun, 29 Mar 2009 14:33:30 -0700
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: "Jignesh K. Shah" <J.K.Shah@Sun.COM>
CC: decibel@decibel.org, Tom Lane <tgl@sss.pgh.pa.us>,
	Scott Carey <scott@richrelevance.com>,
	Kevin Grittner <Kevin.Grittner@wicourts.gov>,
	pgsql-performance@postgresql.org
Subject: Re: Proposal of tunable fix for scalability of 8.4
References: <C5DDBB25.3333%scott@richrelevance.com>
	<29836.1236826066@sss.pgh.pa.us> <49B8861C.2000005@sun.com>
	<1E9C2E4B-4C0C-4343-B244-388DA2047870@decibel.org>
	<49BD67A4.7020106@sun.com>
In-Reply-To: <49BD67A4.7020106@sun.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/15/09 1:40 PM, Jignesh K. Shah wrote:
>
>
> decibel wrote:
>> On Mar 11, 2009, at 10:48 PM, Jignesh K. Shah wrote:
>>> Fair enough.. Well I am now appealing to all who has a fairly decent
>>> sized hardware want to try it out and see whether there are "gains",
>>> "no-changes" or "regressions" based on your workload. Also it will
>>> help if you report number of cpus when you respond back to help
>>> collect feedback.

EAStress (the J2EE benchmark from Spec) would be perfect for this, and 
we (community) have a license for it.

However, EAstress really requires 2-3 J2EE servers to keep the DB server 
busy.

--Josh