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 BCE1E3A4490 for ; Thu, 6 Jan 2005 15:51:31 +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 03879-06 for ; Thu, 6 Jan 2005 15:51:02 +0000 (GMT) Received: from frank.wiles.org (frank.wiles.org [24.124.39.75]) by svr1.postgresql.org (Postfix) with ESMTP id AE06D3A42E4 for ; Thu, 6 Jan 2005 15:51:04 +0000 (GMT) Received: from kungfu (frank.wiles.org [127.0.0.1]) by frank.wiles.org (8.13.1/8.13.1) with SMTP id j06FphOt006583; Thu, 6 Jan 2005 09:51:44 -0600 Date: Thu, 6 Jan 2005 09:52:19 -0600 From: Frank Wiles To: Vinicius Caldeira Carvalho Cc: pgsql-performance@postgresql.org Subject: Re: first postgrreSQL tunning Message-Id: <20050106095219.5a690860.frank@wiles.org> In-Reply-To: <41DD3AF7.6000202@squadra.com.br> References: <41DD3AF7.6000202@squadra.com.br> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/65 X-Sequence-Number: 9755 On Thu, 06 Jan 2005 11:19:51 -0200 Vinicius Caldeira Carvalho wrote: > Hi there! I'm doing my first tunning on my postgreSQL, my server is > for a small app, largest table shall never exceed 10k rows, and less > than 1k transactions/day. So I don't think I should run out of > resources. The machine is a Fedora Core 3.0 with 1gb ran and kernel > 2.6. I'm thinking in having 50 connections limit, so besides > semaphores should I do anything special on kernel parameters. The app > is so small that during late night time almost no one will access so, > I'm thinking in full vacuuming it every day at 1:00AM. > > Any tips are very very welcome :D You'll want to tune shared_buffers and sort_mem. Possibly also effective_cache_size. It really depends on your system. Having tuned a ton of apps to work with PostgreSQL what I usually do is write a small script that does the major resource intensive queries on the database and time it. Tweak a PostgreSQL parameter and re-run, wash, rinse, repeat until I get what I believe is the best performance I can. --------------------------------- Frank Wiles http://www.wiles.org ---------------------------------