Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 9D18164FD5F for ; Mon, 22 Dec 2008 23:49:01 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 92425-07 for ; Mon, 22 Dec 2008 23:48:59 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mail.postgresql.org (Postfix) with ESMTP id 286B164FC18 for ; Mon, 22 Dec 2008 23:48:59 -0400 (AST) Received: by rv-out-0506.google.com with SMTP id b25so3698542rvf.43 for ; Mon, 22 Dec 2008 19:48:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=DCUkOwilmDe1fOU6wzlzXRGtobG09i6YSwWWWj4tyAA=; b=j/OTXv6NH2JftxICw7zOgXyC/HNEukp7qX+J2rzFH+3rNTMxz3HyhyfS7lLlhmsIym 2dhAbCLFpKiD4JcDIMq7QFNfbDtyH4KuV4bg0JBMcxNFnmv2+5YXafQ6zIlNQxuqtEM/ wthBHMQAcq6HxkdPLELs6JGdqpR3LQWvOF074= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PAbfVPb8d40vDH0cJItDVZEjSOU7lDClDwxiE4x2cnQgI3mcuCPtgskZVIyVvK6Y8m MLyor9aCVF5n5RpvN93GaDqVgdPEYd+lWSeaFRQ47LICvsHnGHG4VUj0mVYqL+lv/sLg yXmqnipu5h4QB8eylaL9PrC7oJP65+YbDk+lU= Received: by 10.141.29.18 with SMTP id g18mr3530187rvj.129.1230004137561; Mon, 22 Dec 2008 19:48:57 -0800 (PST) Received: by 10.141.87.11 with HTTP; Mon, 22 Dec 2008 19:48:57 -0800 (PST) Message-ID: <70c01d1d0812221948y41e8e14do78c3f1f4e29acf0@mail.gmail.com> Date: Mon, 22 Dec 2008 19:48:57 -0800 From: "Mark Wong" To: "Kevin Grittner" Subject: Re: dbt-2 tuning results with postgresql-8.3.5 Cc: "pgsql-performance@postgresql.org" , "Gabrielle Roth" , "Selena Deckelmann" In-Reply-To: <494F5D81.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70c01d1d0812201654i5f55150ep619a6c7ff094470@mail.gmail.com> <494F5D81.EE98.0025.0@wicourts.gov> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/199 X-Sequence-Number: 32235 On Mon, Dec 22, 2008 at 7:27 AM, Kevin Grittner wrote: >>>> "Mark Wong" wrote: > >> The DL380 G5 is an 8 core Xeon E5405 with 32GB of >> memory. The MSA70 is a 25-disk 15,000 RPM SAS array, currently >> configured as a 25-disk RAID-0 array. > >> number of connections (250): > >> Moving forward, what other parameters (or combinations of) do people >> feel would be valuable to illustrate with this workload? > > To configure PostgreSQL for OLTP on that hardware, I would strongly > recommend the use of a connection pool which queues requests above > some limit on concurrent queries. My guess is that you'll see best > results with a limit somewhere aound 40, based on my tests indicating > that performance drops off above (cpucount * 2) + spindlecount. Yeah, we are using a homegrown connection concentrator as part of the test kit, but it's not very intelligent. > I wouldn't consider tests of the other parameters as being very useful > before tuning this. This is more or less equivalent to the "engines" > configuration in Sybase, for example. Right, I have the database configured for 250 connections but I'm using 200 of them. I'm pretty sure for this scale factor 200 is more than enough. Nevertheless I should go through the exercise. Regards, Mark