Hi Raph,
We are having the same problem, but without a solution. If you really
solved this problem we will be very grateful, try doing the pull request
as soon as possible.
Nice work!!
Best regards.
Em 02-02-2016 09:29, André Peters escreveu:
Hi, great news! You may create a pull request on Github or use the bug tracker,
I guess. :-)
André
Von meinem iPhone gesendet
Am 02.02.2016 um 11:34 schrieb Raph Weyman <[email protected]>:
Hi all,
Having watched the SOGo daemon repeatedly chomp through all of the RAM and
swap on my server while syncing a large calendar over ActiveSync, I believe I
have discovered the cause.
It's an unconstrained use of the auto-release pool in the method
'processSyncCommands' (file SOGoActiveSyncDispatcher+Sync.m).
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.
I'd like to offer this minor change back for incorporation into future
releases.
What is the etiquette for doing so?
Should I post the patch details to this mailing list?
--
[email protected]
https://inverse.ca/sogo/lists
--
Emílio Fonseca
Development Analyst
Mav Tecnologia - (31) 3211-7777
--
[email protected]
https://inverse.ca/sogo/lists
