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 602248B9EBA for ; Wed, 23 Feb 2005 18:25:09 +0000 (GMT) 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 90011-07 for ; Wed, 23 Feb 2005 18:25:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by svr1.postgresql.org (Postfix) with ESMTP id BC2B58B9EAB for ; Wed, 23 Feb 2005 18:25:04 +0000 (GMT) Received: by wproxy.gmail.com with SMTP id 68so1638449wra for ; Wed, 23 Feb 2005 10:25:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:cc:subject:date:organization:mime-version:content-type:content-transfer-encoding:x-mailer:in-reply-to:x-mimeole:thread-index:message-id; b=L4YZkp4gZJHitJ59PZlkF63Q8Bcx/JBZLN+4dukETySHL9rC5JdCj55V9up5UkbZyLWlKqKIUvZem1oXeDSIBhA5YNhav5HkOcMo3Vve1PE6qwUh0uUzjN+FuIeI4GdAXBLuyfvijNUPobsGFEQ19RMIAqBmE956qBVRjjU9vcE= Received: by 10.54.53.22 with SMTP id b22mr100658wra; Wed, 23 Feb 2005 10:25:04 -0800 (PST) Received: from sbew318anc22 ([200.184.93.96]) by smtp.gmail.com with ESMTP id g2sm364311wra.2005.02.23.10.25.02; Wed, 23 Feb 2005 10:25:04 -0800 (PST) From: "Bruno Almeida do Lago" To: "'Michael Adler'" Cc: Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout Date: Wed, 23 Feb 2005 15:26:18 -0300 Organization: G&P MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050223180338.GA4259@pobox.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcUZ0uJGZ6uw2n4CQ2mGl6iD84LXsgAAa5ww Message-ID: <421cca80.3da18bb5.6940.3b12@smtp.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.09 tagged_above=0 required=5 tests=AWL, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200502/330 X-Sequence-Number: 10659 Is there a real limit for max_connections? Here we've an Oracle server with up to 1200 simultaneous conections over it! "max_connections: exactly like previous versions, this needs to be set to the actual number of simultaneous connections you expect to need. High settings will require more shared memory (shared_buffers). As the per-connection overhead, both from PostgreSQL and the host OS, can be quite high, it's important to use connection pooling if you need to service a large number of users. For example, 150 active connections on a medium-end 32-bit Linux server will consume significant system resources, and 600 is about the limit." C ya, Bruno -----Original Message----- From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Michael Adler Sent: Wednesday, February 23, 2005 3:04 PM To: John Allgood Cc: pgsql-performance@postgresql.org Subject: Re: [PERFORM] Peformance Tuning Opterons/ Hard Disk Layout On Wed, Feb 23, 2005 at 11:39:27AM -0500, John Allgood wrote: > Hello All > > I am setting up a hardware clustering solution. My hardware is Dual > Opteron 550 with 8GB ram. My external storage is a Kingston Fibre > channel Infostation. With 14 15000'k 36GB drives. The OS we are running > is Redhat ES 3.0. Clustering using Redhat Cluster Suite. Postgres > Version is Postgres 7.4.7. We will be setting up about 9 databases which > range in size from 100MB to 2.5GB on the config. The postgres > application is mostly read intensive. What would be the best way to > setup the hardrives on this server. Currently I have it partioned with 2 > seperate raid 5 with 1 failover per raid. I have two database clusters > configured with a seperate postmaster running for each. Running two > postmasters seems like a pain but that is the only way I knew to > seperate the load. I am mostly concerned about disk IO and performance. > Is my current setup a good way to accomplish the best performance or > would it be better to use all the drives in one huge raid five with a > couple of failovers. I have looked around in the archives and found some > info but I would like to here about some of the configs other people are > running and how they have them setup. http://www.powerpostgresql.com/PerfList/ Consider a separate array for pg_xlog. With tablespaces in 8.0, you can isolate much of the IO in a single cluster. -Mike Adler ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org