I was running cyrus as my company mailserver for a while, I saw things start to slowdown when there were more then ~7K messages in one folder (and start to be significant when it got to more then ~20K messages/folder). This was on linux 2.0.x on a pentium 200 with 64MB ram serving ~200 users.
it's a problem, but it's far less of a problem then attempting to parse a unix mail file to get the message you need, that starts to slow down significantly at <1000 messages (on a much faster linux box) David Lang On Mon, 22 Oct 2001, Amos Gouaux wrote: > Date: Mon, 22 Oct 2001 09:03:16 -0500 > From: Amos Gouaux <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: Cyrus and very large folders > > >>>>> On Sun, 21 Oct 2001 23:24:30 -0700, > >>>>> Jurgen Botz <[EMAIL PROTECTED]> (jb) writes: > > jb> At one point in the past I used Netscape Messaging Server (now iPlanet) > jb> and it had this problem at versions less than 4.x. With a few hundred > jb> users, many of whom had mailboxes with a few thousand messages in them, > jb> opening a mailbox was painfully slow. The problem is that normal Unix > > Well, my inbox currently has 3568 messages in it and PINE pops it > open in a jiffy. You need to keep in mind that Cyrus caches things > like the headers. See the four "cyrus.*" files in each folder. > > In fact, I typically use the auto-expire capabilities in Gnus > (news/mail reader for Emacs/XEmacs) and rarely ever manually delete > a message. I could not do this if Cyrus didn't handle large folders > well. > > jb> Has anyone who uses Cyrus in a large organization environment found > jb> this to be a problem? > > How do you define "large"? ;-) I think if you spread your message > store across spindles, you should be okay. > > > -- > Amos >
