Partitioning advice

[Simon Matter]

> Asking differently, is it worth putting the spool metadata on a separate
> partition, considering that the spool itself is already spread among
> several partitions, and thus I/O should be split too?
>
> Has anyone tried both alternatives?

I did a lot of tests but can't remember what the result of my tests were.
At least I decided not to use separate metadata partition, I think because
I didn't have enough disks to really separate the spindles. And one
problem was that my tests were not real life tests on a production server.
I ended up with a classic setup where /var/lib/imap resides on fast local
disks and /var/spool/imap was on SAN.

Simon

>
> Thanks,
> Andre
>
>
> On Thu, 2008-01-24 at 10:21 -0200, Andre Nathan wrote:
>> Hello
>>
>> I'm planning for a new Cyrus install, for which I'll use a multiple
>> partitioning scheme. The idea so far is to have a partion for /
>> and /var/lib/imap (call it the metadata partition), and multiple
>> partitions for the spool data. The idea is to improve I/O by having
>> the /var/lib/imap data on a separate partition.
>>
>> However, I've just read that Cyrus 2.3.x is able to store the spool
>> metadata on diffent partitions. Would it be an advantage to use that
>> feature too, storing these metadata on the metadata partition, together
>> with the /var/lib/imap stuff, or would I only see an improvement if the
>> spool metadata is on yet another partition?
>>
>> Any other advice on partitioning strategies is welcome.
>>
>> Thanks in advance,
>> Andre
>>
>> ----
>> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
>> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
> ----
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>