Hello,
Some suggestions for general guidance:
- Avoid deduplication. Maybe use compression at low level or fast algorithm to
get dedup effect ALSO. With compression you get dynamic sector size also.
- RAIDZn is for space, not for performance. Beware.
- RAIDZn is not cheap to expand.
-
Am 13. August 2017 18:18:15 MESZ schrieb Vincent Fox :
>Compression is a big winner!
>
>We had fast compression on database etc. gzip on the inboxed.
>
>Other than that consider noatime.
Do you mean your cyrus goes "faster" with any kind of ZFS compression enabled?
This is a bit curious to me (i
Compression is a big winner!
We had fast compression on database etc. gzip on the inboxed.
Other than that consider noatime.
Dedup wasn't available back when, and now our Cyrus is gone in favor of
office365.
Good luck
Sent from my iPhone
On Aug 13, 2017, at 00:20, Mikhail T.
mailto:mi+cy.
:
>I'd like to move my current spool from a single (fast) disk to ZFS. Any
>
>suggestions for the filesystem-parameters?
>
>Do I want deduplication, for example? Compression? Recordsize?
We have a few cyrus-imap on ZFS (BSD) within jails.
Each spool got bis own dataset.
We do not use compressi
I'd like to move my current spool from a single (fast) disk to ZFS. Any
suggestions for the filesystem-parameters?
Do I want deduplication, for example? Compression? Recordsize?
Thanks!
-mi
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipe
