I use imapproxy with Horde Webmail here. Assuming the proxy is using cached connections instead of making a new connection each click, then I would look into performance problems within Cyrus itself. It would be interesting to see what IMAP commands Roundcube is issuing to Cyrus. Perhaps it is doing something "stupid" like retrieving all the message bodies on each click? If you haven't already, try enabling telemetry logging for a single user and check the telemetry log files. If you can post some of those logs here, we may be able to identify the problem. Thanks, Andy On Fri, 11 Sep 2015, signaldeveloper@xxxxxxxxx wrote: > I tried imapproxy. It is the same speed. And again, definitely not hardware related. > > I see in the logs in queries the proxy and that works fine but not sure why it's still the same speed. > > > - Paul > >> On Sep 11, 2015, at 2:47 PM, Andrew Morgan <morgan@xxxxxxxx> wrote: >> >>> On Thu, 10 Sep 2015, signaldeveloper@xxxxxxxxx wrote: >>> >>> Is there some type of log I can provide from Cyrus / sasl to help diagnose this better to the kolab guys? Other kolab guys I know say their entropy is right where I'm at and they aren't experiencing these slowness issues. >>> >>> Are their sasl or Cyrus logs I can provide? >> >> Maybe I missed this detail earlier in the thread, but why not run an IMAP proxy to reduce the rate of new connections to Cyrus? Making a new IMAP connection with every click seems abusive! :) >> >> Andy > ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
