Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-25 Thread Pascal Gienger
You wrote: > By the way I tried this on a fully patched > Solaris 10u3 system > and get this notice during boot: > sorry, variable 'zfs_nocacheflush' is not > defined in the 'zfs' module We have Solaris 10 08/07. Also fully patched. Kernel is SunOS 5.10 Generic_120012-14 i86pc This is 10u4

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-24 Thread Vincent Fox
Pascal Gienger wrote: > > [2] in /etc/system: set zfs:zfs_nocacheflush=1 >on a live system using mdb -kw: zfs_nocacheflush/W0t1 By the way I tried this on a fully patched Solaris 10u3 system and get this notice during boot: sorry, variable 'zfs_nocacheflush' is not defined in the 'zfs' modu

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-24 Thread Adam Stephens
Wesley Craig wrote: > On 21 Sep 2007, at 13:36, Pascal Gienger wrote: > >> A proxy would mean another possibility of failure. How stable is >> that proxy daemon? Another two boxes for redundancy? >> > > UMich runs the caching proxy on the host running httpd/webmail. up- > imapproxy is v

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-22 Thread Rob Mueller
> http://cyrus.brong.fastmail.fm/patches/cyrus-statuscache-2.3.8.diff > > This cuts back on meta IO traffic considerably for repeated SELECT > calls on mailboxes which are unchanged. We are in a similar boat, > and it makes a huge difference (also for some other clients) That should be "cuts back

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-22 Thread Alain Spineux
On 9/21/07, Pascal Gienger <[EMAIL PROTECTED]> wrote: > Wesley Craig <[EMAIL PROTECTED]> wrote: > > > I might suggest running a connection caching daemon, up-imapproxy > > springs to mind. LOGIN & SELECT are not exactly lightweight. > > Actually, login is lightweight and never was source of perfor

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-22 Thread Bron Gondwana
On Sat, 22 Sep 2007 14:19:45 +0930, "Daniel O'Connor" <[EMAIL PROTECTED]> said: > On Sat, 22 Sep 2007, Bron Gondwana wrote: > > On Fri, Sep 21, 2007 at 05:53:48PM -0400, Wesley Craig wrote: > > > On 21 Sep 2007, at 13:36, Pascal Gienger wrote: > > > > A proxy would mean another possibility of fail

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Pascal Gienger
Bron Gondwana <[EMAIL PROTECTED]> wrote: > > But yeah, connection caching is nice. Even just the fork overhead > on the backend servers is something we can do without if it's > avoidable. My own Perl IMAP mod_perl routines use this:

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Daniel O'Connor
On Sat, 22 Sep 2007, Bron Gondwana wrote: > On Fri, Sep 21, 2007 at 05:53:48PM -0400, Wesley Craig wrote: > > On 21 Sep 2007, at 13:36, Pascal Gienger wrote: > > > A proxy would mean another possibility of failure. How stable is > > > that proxy daemon? Another two boxes for redundancy? > > > > UMi

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Bron Gondwana
On Fri, Sep 21, 2007 at 05:53:48PM -0400, Wesley Craig wrote: > On 21 Sep 2007, at 13:36, Pascal Gienger wrote: > > A proxy would mean another possibility of failure. How stable is > > that proxy daemon? Another two boxes for redundancy? > > UMich runs the caching proxy on the host running httpd

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Wesley Craig
On 21 Sep 2007, at 13:36, Pascal Gienger wrote: > A proxy would mean another possibility of failure. How stable is > that proxy daemon? Another two boxes for redundancy? UMich runs the caching proxy on the host running httpd/webmail. up- imapproxy is very stable. :wes Cyrus Home Page: ht

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Pascal Gienger
Wesley Craig <[EMAIL PROTECTED]> wrote: > I might suggest running a connection caching daemon, up-imapproxy > springs to mind. LOGIN & SELECT are not exactly lightweight. Actually, login is lightweight and never was source of performance misses. As the webmail applications are "talking" via a p

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Wesley Craig
On 21 Sep 2007, at 01:51, Pascal Gienger wrote: > (*) 100k mailboxes and a webmail application which often LOGINs and > SELECTs, multiple times per webpage reload. I might suggest running a connection caching daemon, up-imapproxy springs to mind. LOGIN & SELECT are not exactly lightweight. :we

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Jarod Watkins
Pascal Gienger wrote: Vincent Fox <[EMAIL PROTECTED]> wrote: Pascal, How many accounts did you have per mail-store? We have 14k(*) users and a failover mailstore. In our SAN we have 3,5T storage reserved, which can be expanded to our needs. We use 2 SAN storages, location-separated

Re: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-21 Thread Bron Gondwana
On Fri, Sep 21, 2007 at 07:51:22AM +0200, Pascal Gienger wrote: > (*) 100k mailboxes and a webmail application which often LOGINs and > SELECTs, multiple times per webpage reload. http://cyrus.brong.fastmail.fm/patches/cyrus-statuscache-2.3.8.diff This cuts back on meta IO traffic considerably f

RE: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-20 Thread Pascal Gienger
Vincent Fox <[EMAIL PROTECTED]> wrote: > Pascal, > > How many accounts did you have per mail-store? We have 14k(*) users and a failover mailstore. In our SAN we have 3,5T storage reserved, which can be expanded to our needs. We use 2 SAN storages, location-separated, so when one location gets f

RE: Cyrus IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-20 Thread Vincent Fox
Pascal, How many accounts did you have per mail-store? Thanks! 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 IMAP 2.3.9 on Solaris 10 with ZFS and SAN

2007-09-20 Thread Pascal Gienger
Just a little note, for those who have perhaps the same problem. We saw performance problems after we switched from a Linux installation to a Solaris 10 cluster connected to our SAN (using scsi_vhci and 2 Qlogic Controllers). Problems arose when real load came to the machine, despite having t