If you want a faster Kolab, read this.

[Brady, Mike]

On 2015-09-11 14:31, signaldeveloper at gmail.com wrote: 

> Mike, 
> 
> If I disable a bunch of the plugins, all of the constant IMAP logins go away as described in my bug: https://issues.kolab.org/show_bug.cgi?id=5219 [1]

Yes I have looked at the bug and as I have stated I do not see this
behaviour, but that wasn't what I asked anyway. 

You have stated that IMAP logins are slow and implied that that there
are those on the Cyrus IMAP mailing list who also think that they are
slow. I take this to mean that an individual login is slow. That there
are more logins than you think there should be is a different (and
perfectly valid) question. 

So I will ask again, with some slightly different words to try an make
my question clearer. How has it been determined that an individual IMAP
login is slow. Slow being a subjective term I am looking for number(s)
that we can objectively compare here. Are the user and sys values on the
USAGE line in the logs the login timings? What do the Cyrus guys think
that these numbers should be in order for them not to be considered
slow? 

> It's odd because only (not in front of me right now) a few of the actual kolab plugins check in EVERY message select. If you disable them, the system runs super fast. I watch as the plugin check in on SQL but they also check in with IMAP. I'm not sure what else to do but the Cyrus guys are telling me kolab may have compiled their SASL not too smart.

What is it that they think is wrong exactly or at least in what area do
they think that there is an issue? 

> At this point I am hoping to hear something from these guys about what's going on. 
> 
> Mike - have you tried following my steps in the bug? You may see a difference just disabling the few plugins (testing obviously, not permanent). Just following the steps I provided and see what happens.

I have not tried this because, as I have said before, I do not see this
behaviour at all. 

To be more specific: 
With the preview pane enabled, if I select (meaning one click) a message
that is not in the cache I see two logins. Using tshark on the Kolab
server it looks like one login fetches the message and one login
accesses the Configuration folder. That is all. I have never seen "one
login per plugin" (which is what I believe you are saying that you are
seeing) when selecting an email. The configuration folder is where tags
are kept and if there are entries in that folder there will be some
searches done within the session for tags. 

Subjectively (I must find out how to get some actual timings), from the
time that I click on a email to the time it is displayed in the preview
pane is about one second. Maybe a little more sometimes. I would love to
get my message display times to be consistently < 1sec. 

> Cyrus guys blamed SASL but also wondered why my entropy was so low. I've done a lot of research over the past few weeks learning about entropy generation and it seems on a normal server it seems to be normal to have 1000 something.. Even on a headless server. My other production servers only have 180 and they're lightning fast. So I'm confused.

My entropy is no better than yours, but it could still be a contributing
factor. 

I do not think that there is a single setting that is going to suddenly
make Kolab perform. It is going to be the sum of a lot of things
starting with the hardware and working up. Every little bit is going to
help. 

Regards 

Mike 

 

Links:
------
[1] https://issues.kolab.org/show_bug.cgi?id=5219
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20150913/f13b3627/attachment.html>