From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Amazon High I/O instances |
Date: | 2012-09-13 21:28:53 |
Message-ID: | 50525015.7000606@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 09/13/12 2:08 PM, Sébastien Lorion wrote:
> I started db creation over, this time with 16GB maintenance_work_mem
> and fsync=off and it does not seem to have a great effect. After again
> 5 hours, during index creation, disk and cpu are barely used: 95% idle
> and 2-3 MB/s writes (150 reads/s, 90 writes/s).
I've never had to set maintenance_work_mem any higher than 1gb for
plenty good enough performance.
whats the %busy on the disk ? if you have a slow disk device (such as
a shared virtual disk), 90 write/sec may be all its good for. MB/s is
fairly meaningless when dealing with random committed writes.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2012-09-13 22:08:47 | Re: Fixing or diagnosing Canceled on identification as a pivot, during write |
Previous Message | Bill Moran | 2012-09-13 21:25:09 | Re: Best free tool for relationship extraction |