Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 33F469FA379 for ; Wed, 13 Dec 2006 23:00:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 42244-04 for ; Wed, 13 Dec 2006 23:00:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 40E4C9FA0B7 for ; Wed, 13 Dec 2006 23:00:51 -0400 (AST) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id kBE30iRx031544 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 13 Dec 2006 19:00:45 -0800 Subject: Re: New to PostgreSQL, performance considerations From: "Joshua D. Drake" To: Josh Berkus Cc: pgsql-performance@postgresql.org, Bruce Momjian , Tom Lane , Alvaro Herrera , Alexander Staubo , Michael Stone In-Reply-To: <200612131836.25713.josh@agliodbs.com> References: <200612140104.kBE14Dx09695@momjian.us> <200612131836.25713.josh@agliodbs.com> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Wed, 13 Dec 2006 19:02:39 -0800 Message-Id: <1166065359.6494.16.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 13 Dec 2006 19:00:46 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/356 X-Sequence-Number: 22412 On Wed, 2006-12-13 at 18:36 -0800, Josh Berkus wrote: > Bruce, > > > pgbench is designed to be a general benchmark, meanining it exercises > > all parts of the system. I am thinking just reexecuting a single SELECT > > over and over again would be a better test of the CPU optimizations. > > Mostly, though, pgbench just gives the I/O system a workout. It's not a > really good general workload. It also will not utilize all cpus on a many cpu machine. We recently found that the only way to *really* test with pgbench was to actually run 4+ copies of pgbench at the same time. J > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate