X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9E5905380D for ; Wed, 27 Apr 2005 20:57:43 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07377-05 for ; Wed, 27 Apr 2005 23:57:36 +0000 (GMT) Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by svr1.postgresql.org (Postfix) with ESMTP id 5E7455364B for ; Wed, 27 Apr 2005 20:57:35 -0300 (ADT) X-EthosMedia-Virus-Scanned: no infections found Received: from [67.103.46.98] (account josh@agliodbs.com HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 7294630; Wed, 27 Apr 2005 16:59:36 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Greg Stark Subject: Re: Why is this system swapping? Date: Wed, 27 Apr 2005 17:02:49 -0700 User-Agent: KMail/1.7.1 Cc: Jeff , "Anjan Dave" , pgsql-performance@postgresql.org References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509899C@vt-pe2550-001.vantage.vantage.com> <87r7gv3hrx.fsf@stark.xeocode.com> In-Reply-To: <87r7gv3hrx.fsf@stark.xeocode.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504271702.49992.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/751 X-Sequence-Number: 12148 Greg, > In fact I think it's generally superior to having a layer like pgpool > having to hand off all your database communication. Having to do an extra > context switch to handle every database communication is crazy. Although, one of their issues is that their database connection pooling is per-server. Which means that a safety margin of pre-allocated connections (something they need since they get bursts of 1000 new users in a few seconds) has to be maintained per server, increasing the total number of connections. So a pooling system that allowed them to hold 100 free connections centrally rather than 10 per server might be a win. Better would be getting some of this stuff offloaded onto database replication slaves. -- --Josh Josh Berkus Aglio Database Solutions San Francisco