| From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
|---|---|
| To: | "Chris Mair" <list(at)1006(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Cc: | markir(at)paradise(dot)net(dot)nz, "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Subject: | Re: bad performance on Solaris 10 |
| Date: | 2006-04-05 21:40:14 |
| Message-ID: | C059874E.20ECE%llonergan@greenplum.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Chris,
On 4/5/06 2:31 PM, "Chris Mair" <list(at)1006(dot)org> wrote:
> Doing what http://blogs.sun.com/roller/page/jkshah suggests:
> wal_sync_method = fsync (unchanged)
> wal_buffers = 128 (was 8)
> checkpoint_segments = 128 (was 3)
> bgwriter_all_percent = 0 (was 0.333)
> bgwriter_all_maxpages = 0 (was 5)
> and leaving everything else default (solarispackages from pgfoundry)
> increased performance ~ 7 times!
In the recent past, Jignesh Shaw of Sun MDE discovered that changing the
bgwriter_* parameters to zero had a dramatic positive impact on performance.
There are also some critical UFS kernel tuning parameters to set, you should
find those in his blog.
We found and fixed some libpq issues with Solaris that were also critical -
they should be in 8.1.3 I think.
- Luke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan Casero (FL FLC) | 2006-04-05 21:45:03 | Re: Sun Fire T2000 and PostgreSQL 8.1.3 |
| Previous Message | Luke Lonergan | 2006-04-05 21:37:28 | Re: Sun Fire T2000 and PostgreSQL 8.1.3 |