Tickets :: Comment on [#11807] Kolab backend: Parsing is a memory hog

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .__ .__ __ \| \|[__)\| \\| \/ ` \|__\|[__)\|__/\|__/\__.
Comment	> Hi, > > I've done some stress testing with 6.000+ contacts on a Kolab backend. > Tests are done with H4 and H5. > > H4 consumes about 150MB memory during IMAP retrieval + parse + display. > > H5 consumes 140MB memory during IMAP retrieval and 750MB+ during parse. Argh. > Once the parsed contacts are cached, simple clicks in turba consume > about 150MB. > > We probably do something very memory unfriendly either in the Kolab > driver or in the Kolab_Storage framework. > > This is just for the record, the issue is of low priority for now. > > Thomas >
Attachment
Watch this ticket