Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D128F9FA38F for ; Fri, 29 Dec 2006 17:25:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 00554-05 for ; Fri, 29 Dec 2006 17:25:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.trinitydigital.com.au (unknown [202.134.38.99]) by postgresql.org (Postfix) with ESMTP id 440599FA372 for ; Fri, 29 Dec 2006 17:25:18 -0400 (AST) Received: from [172.17.73.3] (unknown [202.134.38.110]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.trinitydigital.com.au (Postfix) with ESMTP id BD7013CE; Sat, 30 Dec 2006 08:24:46 +1100 (EST) Message-ID: <459587B8.8070507@pws.com.au> Date: Sat, 30 Dec 2006 08:25:12 +1100 From: Russell Smith User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: sebaioni-postgresql@yahoo.com.ar CC: Performance PostgreSQL Subject: Re: Backup/Restore too slow References: <20061229180355.31522.qmail@web36104.mail.mud.yahoo.com> In-Reply-To: <20061229180355.31522.qmail@web36104.mail.mud.yahoo.com> Content-Type: multipart/alternative; boundary="------------040100020506080805030005" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/535 X-Sequence-Number: 22591 This is a multi-part message in MIME format. --------------040100020506080805030005 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sebastián Baioni wrote: > Thanks for answering. > This is my configuration: > # - Memory - > > shared_buffers = 1000 # min 16, at least max_connections*2, 8KB > each > #work_mem = 1024 # min 64, size in KB > #maintenance_work_mem = 16384 # min 1024, size in KB > #max_stack_depth = 2048 # min 100, size in KB > > The PC where we are runing PostgreSQL server is: > AMD Athlon(tm) 64 Processor > 3000+ > 1.79 GHz, 1.93 GB RAM > with WindowsXP Proffesional, Version 2002 Service Pack 2. > > How should we set it? Shared buffers even on a workstation should be higher than 1000 if you want some performance. It depends how much memory you have spare to use for PostgreSQL. But something like shared_buffers = 20000 maintenance_work_mem = 256000 Will certainly give you a performance boost. You will have to adjust those figures based on whatever else you are doing on the machine. Russell Smith. > > Thanks a lot! > Sebastián > > */Tom Lane /* escribió: > > Rod Taylor writes: > > Rebuilding the indexes or integrity confirmations are probably > taking > > most of the time. > > > What is your work_mem setting? > > maintenance_work_mem is the thing to look at, actually. I concur that > bumping it up might help. > > regards, tom lane > > ---------------------------(end of > broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > > __________________________________________________ > Correo Yahoo! > Espacio para todos tus mensajes, antivirus y antispam ¡gratis! > ¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar > --------------040100020506080805030005 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sebastián Baioni wrote:
Thanks for answering.
This is my configuration:
# - Memory -

shared_buffers = 1000        # min 16, at least max_connections*2, 8KB each
#work_mem = 1024        # min 64, size in KB
#maintenance_work_mem = 16384    # min 1024, size in KB
#max_stack_depth = 2048        # min 100, size in KB

The PC where we are runing PostgreSQL server is:
AMD Athlon(tm) 64 Processor
3000+
1.79 GHz, 1.93 GB RAM
with WindowsXP Proffesional, Version 2002 Service Pack 2.

How should we set it?
Shared buffers even on a workstation should be higher than 1000 if you want some performance.  It depends how much memory you have spare to use for PostgreSQL.  But something like
shared_buffers = 20000
maintenance_work_mem = 256000

Will certainly give you a performance boost.  You will have to adjust those figures based on whatever else you are doing on the machine.

Russell Smith.

Thanks a lot!
     Sebastián

Tom Lane <tgl@sss.pgh.pa.us> escribió:
Rod Taylor writes:
> Rebuilding the indexes or integrity confirmations are probably taking
> most of the time.

> What is your work_mem setting?

maintenance_work_mem is the thing to look at, actually. I concur that
bumping it up might help.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar


--------------040100020506080805030005--