Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B9C8C9FB427 for ; Mon, 21 May 2007 18:05:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 91698-03 for ; Mon, 21 May 2007 18:05:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 711839FB30E for ; Mon, 21 May 2007 18:05:26 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 75E5C56447; Mon, 21 May 2007 16:05:25 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 21 May 2007 16:05:22 -0500 Date: Mon, 21 May 2007 16:05:22 -0500 From: "Jim C. Nasby" To: PFC Cc: pgsql-performance@postgresql.org Subject: Re: Postgres Benchmark Results Message-ID: <20070521210522.GN62346@nasby.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070521:lists@peufeu.com::dML8gFPmJtW8LBq7:03ZSd X-Hashcash: 1:20:070521:pgsql-performance@postgresql.org::e81j5lhgCLpjFHgz:00000 000000000000000000000000DIJ9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/403 X-Sequence-Number: 24793 On Sun, May 20, 2007 at 04:58:45PM +0200, PFC wrote: > > I felt the world needed a new benchmark ;) > So : Forum style benchmark with simulation of many users posting and > viewing forums and topics on a PHP website. > > http://home.peufeu.com/ftsbench/forum1.png Any chance of publishing your benchmark code so others can do testing? It sounds like a useful, well-thought-out benchmark (even if it is rather specialized). Also, I think it's important for you to track how long it takes to respond to requests, both average and maximum. In a web application no one's going to care if you're doing 1000TPS if it means that every time you click on something it takes 15 seconds to get the next page back. With network round-trip times and what-not considered I'd say you don't want it to take any more than 200-500ms between when a request hits a webserver and when the last bit of data has gone back to the client. I'm guessing that there's about 600MB of memory available for disk caching? (Well, 600MB minus whatever shared_buffers is set to). -- Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)