Hello Anton,
Thursday, October 12, 2006, 11:45:40 PM, you wrote:
ABR> Yes, set the block size to 8K, to avoid a read-modify-write cycle inside
ZFS.
Unfortunately it won't help on 06/06 until patch is released to fix a
bug (not to read old block if it's "overwritten"). However it still is
wise t
Yes, set the block size to 8K, to avoid a read-modify-write cycle inside ZFS.
As you suggest, using a separate mirror for the transaction log will only be
useful if you're on different disks -- otherwise you will be forcing the disk
head to move back and forth between slices each time you write.
Quite helpful, thank you.
I think I should set the zfs mirror block size to 8K to match it with db, right
?
and do you think I should create another zfs mirror for transaction log of
pgsql ? or is this only useful if I create zfs mirror on a different set of
disks but not slices ?
Mete
Thi
Mirroring will give you the best performance for small write operations.
If you can get by with two disks, I’d divide each of them into two slices, s0
and s1, say. Set up an SVM mirror between d0s0 and d1s0 and use that for your
root. Set up a ZFS mirror between d0s1 and d1s1 and use that for yo
