Re: Cyrus mail spool entirely on SSD - tiered storage

2016-10-23 Thread ellie timoney via Info-cyrus
On Sat, Oct 22, 2016, at 10:25 AM, Rob N ★ via Info-cyrus wrote: > The docs suggest this feature is in the currently-unreleased Cyrus 3.0 > series. That's probably true, but I can't be sure (FastMail runs the > current dev/master branch, so we're ahead of 3.0). It'll be well worth > the upgrade

Re: Cyrus mail spool entirely on SSD - tiered storage

2016-10-21 Thread Rob N ★ via Info-cyrus
On Fri, 21 Oct 2016, at 08:46 PM, Vladislav Kurz via Info-cyrus wrote: > would you be so kind and point to some info (docs, howtos) about cyrus > tiered storage? All I found is > http://www.cyrusimap.org/~vanmeeuwen/imap/features/mail-spool-partitions.html > but that seem to be quite tedious to

Re: Cyrus mail spool entirely on SSD - tiered storage

2016-10-21 Thread Vladislav Kurz via Info-cyrus
On 10/21/16 10:47, Rob N ★ via Info-cyrus wrote: > At FastMail we have our mail spools on SSDs, in RAID10. We use Intel DC > S3700 which, while on the expensive side, have been incredibly reliable > and fast. They're all still 6G SATA; we're still looking at NVMe (with > some enthusiasm). > > We

Re: Cyrus mail spool entirely on SSD

2016-10-21 Thread Rob N ★ via Info-cyrus
On Thu, 20 Oct 2016, at 05:28 AM, Michael Ulitskiy via Info-cyrus wrote: > My question is: assuming cost is not an issue, would it be advisable > to put an entire cyrus mail spool on SSD? > I'm thinking about combinining multiple SSDs into RAID10 to further > increase performance. At FastMail we

Re: Cyrus mail spool entirely on SSD

2016-10-20 Thread Shawn Bakhtiar via Info-cyrus
I actually just migrated our Cyrus (IMAP) server and was looking into this same questions. I think SSD's are great! Especially in laptops where the drive is susceptible to sudden changes in inertia (in spinners this can lead to physical mechanical damage, but SSD's are immune), not to mention

Cyrus mail spool entirely on SSD

2016-10-19 Thread Michael Ulitskiy via Info-cyrus
Hello, I have a task to build a mail server with the following requirements: 1. ~ hundred mailboxes with up to 10G of data each 2. several mailboxes that may grow up to 100G each 3. client insists that splitting data into folders is inconvenient to them and so all/most of that data will likely