Hi Maurizo, Technically, even if you were using duplicate suppression it would not be a huge loss to store it on a local filesystem. You don't usually see duplicate id's unless someone's MTA goes bonkers; or their MUA is stupid; oh and SPAM. So yeah go for it, that'll save you a good deal of heartache. On May 19, 2008, at 3:18 AM, Maurizio Lo Bosco wrote: >>> Using the flat configuration for the mailbox.db the slow start >>> disapepars. May I use a flat database for 4300+ mailbox? >>> Do you think I could have other performance problems in >>> delivery/accessing the mailbox? >> >> I considered creating a GFS spool for a 50000 mailbox system, but >> during >> testing, the GFS lock overhead would've been too much during delivery >> peaks. Probably had to do mostly with delivery.db locking. > > so far, with 4300+ users it is safe to use a flat database for the > mailbox.db > but I will encounter issues with the delivery. > If I'm not wrong the delivery.db database is reported as > duplicate_db in the > imapd.conf and it is not possible to set it as flat. We don't use the > suppression capability of the cyrus ( a bug of the outlook message > id in the > read_confirm&reply ) so It could be safe to put 2 separate database > on the > local FS. Is this correct? > > Regards > Maurizio > ---- > 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:48315d3550081699917803! > > ---- 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
