On Tue, 29 Jul 2008, Francisco Reyes wrote:
Besides maintenance_work_mem, what else can be changed to improve index
creation?
Very large values there haven't been all that helpful for me. I've gotten
better results in this area giving more of the unused memory to
shared_buffers (which you d
On 3:19 pm 07/29/08 Alan Hodgson <[EMAIL PROTECTED]> wrote:
> sure you only have 4 cores? Hyper-threading?
It seems Hyperthreading is on in that machine. Going to see if I can have
it turned off.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subsc
On Tuesday 29 July 2008, "Francisco Reyes" <[EMAIL PROTECTED]> wrote:
> On 2:53 pm 07/29/08 Alan Hodgson <[EMAIL PROTECTED]> wrote:
> > --sar 2 30
>
> Linux 2.6.9-42.ELsmp (trans03) 07/29/2008
>
> 12:58:09 PM CPU %user %nice %system %iowait %idle
> 12:58:11 PM all 1
On 2:53 pm 07/29/08 Alan Hodgson <[EMAIL PROTECTED]> wrote:
> --sar 2 30
Linux 2.6.9-42.ELsmp (trans03) 07/29/2008
12:58:09 PM CPU %user %nice %system %iowait %idle
12:58:11 PM all 12.44 0.00 0.06 0.00 87.50
12:58:13 PM all 12.44 0
On Tuesday 29 July 2008, "Francisco Reyes" <[EMAIL PROTECTED]> wrote:
> Besides maintenance_work_mem, what else can be changed to improve index
> creation?
>
Depends where the bottleneck is.
1 CPU core 100% user/system = buy faster CPU cores.
System in I/O wait = upgrade disk channel.
--
Alan
Besides maintenance_work_mem, what else can be changed to improve index
creation?
I just did two tests. One with maintenance_work_mem=128MB and another with
maintenance_work_mem=1GB. Out of 3 single column index, 2 took slightly
longer with the higher value and a third took almost the same.
12GB
