On Sat, Nov 12, 2011 at 12:35:26AM +0000, Ed W wrote:
>
> Quick question: What does perdition buy you versus not having it?
>
> The dovecot author suspected that logins were so fast that a persistent
> proxy would likely have little performance advantage - do you measure
> otherwise?
Interesting... as I seem to experience slow initial connect (getting the
body of the first message I select after logging in takes seconds) when
using up-imapproxy, but everything seems quick afterwards. If I have
sogod talk to the imap-servers directly (still trough dovecot-director),
everything is quick always. But I've been the only sogo user active when
testing thism and am worried that this might change once we put heavy
load on it..
I've also noticed there is a NGImap4DisableIMAP4Pooling setting which is
disabled by default, but I haven't found any documentation for it other
than the bugrapport which seems to indicate it should be used if one is
not using an imapproxy:
http://sogo.nu/bugs/view.php?id=1243
and the "NEWS" entry:
- IMAP connection pooling is disabled by default to avoid flooding the
IMAP
servers in multi-process environments (NGImap4DisableIMAP4Pooling now
set
to "YES" by default)
I don't understand what "multi-process environments" is referring to here..?
Does anybody have any comments for if imapproxy is needed or not for
dovecot backend, and if one should use IMAP4Pooling in sogo when not
using an imapproxy?
-jf
--
users@sogo.nu
https://inverse.ca/sogo/lists
