If you want a faster Kolab, read this.

[Paul Bronson]

Christian - please add this to the bug report:
https://issues.kolab.org/show_bug.cgi?id=5219

Andy, I tried that but when i start the service it instantly dies and says
sub system is locked?

On Fri, Sep 11, 2015 at 12:25 PM, Christian Hügel <
christian.huegel at stonebyte.de> wrote:

> Hi,
>
> for everyone interested, these are my caching settings:
>
>  // Caching and storage settings
>     $config['imap_cache'] = 'memcache';
>     $config['memcache_hosts'] = array('localhost:11211');
>     $config['session_storage'] = 'memcache';
>     //$config['imap_cache'] = null;
>     $config['imap_cache_ttl'] = '20d';
>     $config['messages_cache'] = 'memcache';
>     $config['message_cache_ttl'] = '20d';
>
>
> Christian
>
> Am 08.09.2015 um 23:51 schrieb signaldeveloper at gmail.com:
> > Hi Christian,
> >
> > I basically installed memcache and just changed 'DB' to 'memcache' in
> the kolab config. This seemed to give me a small boost but I think I'll
> feel the better boost when I start piling on users.
> >
> > I for some reason couldn't get memcache to work with "session_storage"
> though, it just gives me a white screen. Let me know if you need more in
> depth directions!
> >
> > If anyone has varnish setup please let me know if love to know how to
> get that working with roundcube!
> >
> >
> >
> > - Paul
> >
> >
> >
> >> On Sep 8, 2015, at 12:09 PM, Christian Hügel <
> christian.huegel at stonebyte.de> wrote:
> >>
> >> OK, i got you right now :) You mentioned a performance boost using
> >> memcached. Can you point me a documentation enabling this?
> >> Thanks
> >>
> >>> Am 08.09.2015 um 17:54 schrieb signaldeveloper at gmail.com:
> >>> Christian,
> >>>
> >>> Obviously. This is meant more as a bug test case not as a fix.
> >>>
> >>>
> >>>
> >>>> On Sep 8, 2015, at 11:46 AM, Christian Hügel <
> christian.huegel at stonebyte.de> wrote:
> >>>>
> >>>> I also have a major performance problem although with kolab 3.2 but I
> do
> >>>> not see the point in deactivating those plugins; it would´ t be a
> kolab
> >>>> server anymore instead just an ordinary imap server. So this
> workaround
> >>>> is a "no go"
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Christian
> >>>>
> >>>>> Am 07.09.2015 um 20:55 schrieb Paul Bronson:
> >>>>> Hi guys, (happy labor day!)
> >>>>>
> >>>>> As you've probably seen me asking a thousand questions about slowness
> >>>>> for my brand new kolab 3.4, here's what my few weeks of research has
> >>>>> come up with... And hopefully this will work for all of you as well,
> or
> >>>>> something you can try and replicate on your end:
> >>>>>
> >>>>> A few kolab plugins are initiating an imap connection every time the
> >>>>> user simply tries to read a message. Those plugins are:
> >>>>>
> >>>>> kolab_addressbook
> >>>>> kolab_notes
> >>>>> kolab_tags
> >>>>> tasklist
> >>>>>
> >>>>> If you disable ALL (not one) of these plugins, watch how magically
> fast
> >>>>> clicking on a message is. You will also notice logs in your
> >>>>> var/log/maillog such as this disappear:
> >>>>>
> >>>>>
> >>>>> Sep 7 13:59:55 es1 imap[18657]: USAGE tperson at domain.info
> >>>>> <mailto:tperson at domain.info>user: 0.004000 sys: 0.007999
> >>>>>
> >>>>> Sep  7 14:00:55 es1 imap[18657]: login: localhost [::1]
> tperson at domain.info <mailto:tperson at domain.info> PLAIN User logged in
> SESSIONID=<es1.domain.com-18657-1441648854-1-17261199637593060143>
> >>>>>
> >>>>> These above log entries will however happen when you go to different
> >>>>> folders, but simply just single clicking a message to see it on the
> >>>>> preview pane will no longer log the entry.
> >>>>>
> >>>>>
> >>>>> I have also seen a HUGE improvement from memcache as well. (now that
> >>>>> instead of opening a new connection, it can now actually check
> against
> >>>>> memcache for a cache'd version) I also went to vast lands to try to
> make
> >>>>> cyrus faster thinking that was the problem, but I think this was the
> key!
> >>>>>
> >>>>>
> >>>>> I've logged a bug for this:
> >>>>>
> >>>>> https://issues.kolab.org/show_bug.cgi?id=5219
> >>>>>
> >>>>>
> >>>>> Hopefully this will be an easy fix for the team!
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> users mailing list
> >>>>> users at lists.kolab.org
> >>>>> https://lists.kolab.org/mailman/listinfo/users
> >>>>
> >>>> --
> >>>> GPG-Key: 1F814CFD
> >>>>
> >>>> _______________________________________________
> >>>> users mailing list
> >>>> users at lists.kolab.org
> >>>> https://lists.kolab.org/mailman/listinfo/users
> >>> _______________________________________________
> >>> users mailing list
> >>> users at lists.kolab.org
> >>> https://lists.kolab.org/mailman/listinfo/users
> >>
> >> --
> >> GPG-Key: 1F814CFD
> >>
> >> _______________________________________________
> >> users mailing list
> >> users at lists.kolab.org
> >> https://lists.kolab.org/mailman/listinfo/users
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> >
>
> --
> GPG-Key: 1F814CFD
>
>
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20150911/398ef5bf/attachment-0001.html>