Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Bron Gondwana via Info-cyrus
On Fri, Jul 15, 2016, at 23:52, Bron Gondwana via Info-cyrus wrote: > On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote: > > So if the issue apparently lies with twoskip, can we keep our dbs using > > skiplist and do the 2.4 -> 2.5 upgrade? Is it possible -h could revert > > back

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Andy Dorman via Info-cyrus
On 07/15/2016 08:52 AM, Bron Gondwana via Info-cyrus wrote: On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote: So if the issue apparently lies with twoskip, can we keep our dbs using skiplist and do the 2.4 -> 2.5 upgrade? Is it possible -h could revert back to skiplist? You ca

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Bron Gondwana via Info-cyrus
On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote: > So if the issue apparently lies with twoskip, can we keep our dbs using > skiplist and do the 2.4 -> 2.5 upgrade? Is it possible -h could revert > back to skiplist? You can convert a db back just by changing the setting in imap

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Andy Dorman via Info-cyrus
On 07/15/2016 08:11 AM, Bron Gondwana via Info-cyrus wrote: So we've discussed this at length in #cyrus on freenode, and concluded that the issue is that twoskip is doing far too many munmap / mmap calls during an unlocked foreach (which is what the LIST command uses). I've filed a bug: https

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Bron Gondwana via Info-cyrus
So we've discussed this at length in #cyrus on freenode, and concluded that the issue is that twoskip is doing far too many munmap / mmap calls during an unlocked foreach (which is what the LIST command uses). I've filed a bug: https://github.com/cyrusimap/cyrus-imapd/issues/5 And I'm looking

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Bron Gondwana via Info-cyrus
On Fri, Jul 15, 2016, at 23:03, Kenneth Marshall via Info-cyrus wrote: > On Fri, Jul 15, 2016 at 10:34:53PM +1000, Bron Gondwana via Info-cyrus wrote: > > Squatter indexes will be broken without the latest patches on the 2.5 > > branch. The data gets indexed differently, and I had to patch the sq

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Kenneth Marshall via Info-cyrus
On Fri, Jul 15, 2016 at 10:34:53PM +1000, Bron Gondwana via Info-cyrus wrote: > Squatter indexes will be broken without the latest patches on the 2.5 branch. > The data gets indexed differently, and I had to patch the squatter code to > search both styles. > > Bron. > Hi, Does this problem al

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Bron Gondwana via Info-cyrus
Squatter indexes will be broken without the latest patches on the 2.5 branch. The data gets indexed differently, and I had to patch the squatter code to search both styles. Bron. On Fri, Jul 15, 2016, at 22:17, Andre Felipe Machado via Info-cyrus wrote: > Hello, > Maybe, after such upgrade, sq

Re: Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Andre Felipe Machado via Info-cyrus
Hello, Maybe, after such upgrade, squatter metadata indexes were lost and you should run an incremental squatter again on your mailboxes. Even before the scheduled run at events section on /etc/cyrus.conf. Regards. Andre Felipe Hynek Schlawack via Info-cyrus wrote .. > Hello, > > we’ve update

Huge performance problems after updating from 2.4 to 2.5.8

2016-07-15 Thread Hynek Schlawack via Info-cyrus
Hello, we’ve updated one of our Cyrus IMAP backends from 2.4 to 2.5.8 on FreeBSD 10.3 with ZFS and now we have an operational emergency. Cyrus IMAPd starts fine and keeps working for about 5 to 20 minutes (rather sluggishly tho). At some point the server load starts growing and explodes event