From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com> |
Cc: | Benjamin Smith <lists(at)benjamindsmith(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgresql 9.4 and ZFS? |
Date: | 2015-10-02 19:07:16 |
Message-ID: | 560ED5E4.5060801@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/1/15 8:04 PM, Joseph Kregloh wrote:
> In either case you are still "bottlenecked" by the speed of the write
> from RAM to the zpool. Now for a small database with not many writes a
> ZIL would be awesome. But on a write heavy database you will be
> acknowledging more writes because of the ZIL that what you are
> physically able to write from RAM to zpool, thereby degrading performance.
Unless ZFS lies about fsync, you'll have to wait for writes to go
somewhere, either the main pool or the ZIL. Because the ZIL is
effectively write-only, having a ZIL could significantly reduce fsync
latency because it's a) only writing and b) writing sequentially.
Essentially, it's the same idea as having a separate pg_xlog partition
(except that depending on your setup there may well be pg_xlog read
activity as well).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-10-02 19:13:09 | Re: Serialization errors despite KEY SHARE/NO KEY UPDATE |
Previous Message | Kevin Grittner | 2015-10-02 19:03:51 | Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type? |