| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Joachim Worringen <joachim(dot)worringen(at)iathh(dot)de> |
| Cc: | postgresql performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: optimal ZFS filesystem on JBOD layout |
| Date: | 2010-07-01 14:15:16 |
| Message-ID: | 4C2CA2F4.8080501@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Joachim Worringen wrote:
> Potential issues that I see:
> - the ZFS ZIL will not benefit from a BBU (as it is connected to the
> backplane, driven by the onboard-RAID), and might be too small (32GB
> for ~2TB of data with lots of writes)?
This is a somewhat unpredictable setup. The conservative approach would
be to break two disks out of the larger array for the ZIL, running
through the battery-backed cache, rather than using the SSD drives for
that. The best way IMHO to use SSD for PostgreSQL is to put your large
indexes on it, so that even if the drive does the wrong thing when you
write and the index gets corrupted you can always rebuild them rather
than suffer data loss. Also, index writes really benefit from being on
something with low seek times, moreso than the ZIL or WAL.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-07-01 16:37:51 | Re: how to (temporarily) disable/minimize benefits of disk block cache or postgresql shared buffer |
| Previous Message | Joachim Worringen | 2010-07-01 13:14:32 | optimal ZFS filesystem on JBOD layout |