Tom Lane <tgl 'at' sss.pgh.pa.us> writes:
> Guillaume Cottenceau <gc(at)mnc(dot)ch> writes:
>> I have made a comparison restoring a production dump with default
>> and large maintenance_work_mem. The speedup improvement here is
>> only of 5% (12'30 => 11'50).
>> Apprently, on the restored database, data is 1337 MB and
>> indexes 644 MB. Pg is 8.2.3, checkpoint_segments 3,
>> maintenance_work_mem default (16MB) then 512MB, shared_buffers
>> 384MB. It is rather slow disks (Dell's LSI Logic RAID1), hdparm
>> reports 82 MB/sec for reads.
> The main thing that jumps out at me is that boosting checkpoint_segments
> would probably help. I tend to set it to 30 or so (note that this
> corresponds to about 1GB taken up by pg_xlog).
Interestingly, from a bzipped dump, there is no win; however,
from an uncompressed dump, increasing checkpoint_segments from 3
to 30 decreases clock time from 9'50 to 8'30 (15% if I'm
In response to
pgsql-performance by date
|Next:||From: Moritz Onken||Date: 2008-02-22 15:42:29|
|Subject: store A LOT of 3-tuples for comparisons|
|Previous:||From: Mark Kirkwood||Date: 2008-02-22 05:10:18|
|Subject: Re: 4s query want to run faster|