If you want a faster Kolab, read this.

Andrew Morgan morgan at orst.edu
Mon Sep 14 17:52:03 EDT 2015


On Sat, 12 Sep 2015, Paul Bronson wrote:

> Cyrus gurus - can you help us diagnose the IMAP debug below that I gave and
> help us understand the slow down. I am no imap pro, but the imap_debug
> below seems to show a lot of in-and-out's for a single message click. Again
> this is roundcube, centos 6, kolab 3.4, cyrus version:

The debug log shows that the connection and execution of all those 
commands took place in about 1-2 seconds (19:53:31 - 19:53:32).

Here is a summary of the commands the client issued:

A0001 STARTTLS
A0002 CAPABILITY
A0003 ID ("name" "Roundcube" "version" "1.1.2" "php" "5.3.3" "os" "Linux" "command" "/webmail/8d61c34e132a834f/?_task=mail&_action=preview&_uid=11&_mbox=INBOX&_framed=1&_caps=pdf%3D1%2Cflash%3D1%2Ctif%3D0")
A0004 AUTHENTICATE PLAIN ****** [57]
A0005 GETMETADATA
A0006 LIST ""
A0007 MYRIGHTS
A0008 SELECT Configuration
A0009 LSUB "" "*"
A0010 LIST "" "*"
A0011 GETMETADATA Archive (/private/vendor/kolab/folder-type/shared/vendor/kolab/folder-type)
A0012 MYRIGHTS Tasks
A0013 GETMETADATA Tasks (/private/vendor/kolab/displayname/shared/vendor/kolab/displayname)
A0014 GETMETADATA Tasks (/private/vendor/kolab/color/shared/vendor/kolab/color)
A0015 MYRIGHTS Contacts
A0016 MYRIGHTS "Contacts/Personal Contacts"
A0017 GETMETADATA Contacts (/private/vendor/kolab/displayname/shared/vendor/kolab/displayname)
A0018 GETMETADATA "Contacts/Personal Contacts" (/private/vendor/kolab/displayname/shared/vendor/kolab/displayname)
A0019 GETMETADATA Contacts (/private/vendor/kolab/uniqueid/shared/vendor/cmu/cyrus-imapd/uniqueid/shared/vendor/kolab/uniqueid)
A0020 GETMETADATA "Contacts/Personal Contacts" (/private/vendor/kolab/uniqueid/shared/vendor/cmu/cyrus-imapd/uniqueid/shared/vendor/kolab/uniqueid)
A0021 SELECT Contacts
A0022 LOGOUT

1-2 seconds for all those commands is pretty damn fast.  I don't know if 
that generates much disk I/O, but there must be at least a few I/Os 
required to do that.

I'm with you - the place to optimize this is in Kolab, possibly with in 
conjuction with an imapproxy.

 	Andy


More information about the Info-cyrus mailing list