Cyrus - GFS slow start and poor performace

[Scott Likens]

Going to toss in my 10 cents.

I'm assuming the GFS is the same lun/id on both servers, and you are  
using GFS to read-write between 2 or more servers.

You could try OCFS2 instead of GFS... Other then that the only thing I  
can think of is using DRBD in a read-write configuration.  However  
that would be using 2 lun/id's instead of only 1.

However I imagine the results will be more or less the same, as GFS2  
and OCFS2 may handle reads and writes to ensure accuracy?


On May 14, 2008, at 7:46 AM, Wesley Craig wrote:

> Given that he's got two machines, I might suggest mupdate_config:
> replicated and definitely have mailboxes.db on local disk.
>
> :wes
>
> On 14 May 2008, at 06:30, Bron Gondwana wrote:
>> Depending on your requirements, it may make sense to place your
>> mailboxes.db on local
>> disk (it's pretty small) and regularly copy/rsync it onto your GFS
>> partition.  Worst
>> case you lose a couple of mailboxes.db records in a crash.  Depends
>> what you can afford
>> to lose.  You could probably stat the file every second and copy it
>> on any change pretty
>> cheaply and risk losing at most the last second's changes (it
>> doesn't change often)
>
> ----
> 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
>
>
> !DSPAM:482b00dc195276105139502!
>
>