From: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
---|---|
To: | sebaioni-postgresql(at)yahoo(dot)com(dot)ar |
Cc: | Performance PostgreSQL <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Backup/Restore too slow |
Date: | 2006-12-29 21:25:12 |
Message-ID: | 459587B8.8070507@pws.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)sss(dot)pgh(dot)pa(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-12-29 22:07:47 | Re: High update activity, PostgreSQL vs BigDBMS |
Previous Message | Simon Riggs | 2006-12-29 18:18:18 | Re: URGENT: Out of disk space pg_xlog |