On 2016-02-02 05:34, Raph Weyman wrote:
By adding a locally controlled auto-release pool to the inner 'for' loop in
this function, the memory consumption of the daemon during the same ActiveSync
calendar synchronisation stays within 50K or so.
Much saner than the multi-gigabytes it was consuming before.
If it was consuming multi-gigabytes, that's because the sync response
being generate was enormous.
A local pool might help a bit, but the root of the issue is a
misconfiguration of the SOGoMaximumSyncResponseSize and
SOGoMaximumSyncWindowSize.
For example, if you have 1000 email folders (like I do) and you launch
Outlook 2013, it'll ask for 512 messages for each folder. You can end up
initially sending back 512 000 mails.
Anyway, create the PR and we'll look at it. As I said, a local pool
might help in some corner-cases.
Thanks,
--
Ludovic Marcotte
[email protected] :: +1.514.755.3630 :: http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence
(http://packetfence.org)
--
[email protected]
https://inverse.ca/sogo/lists
