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

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11807
------------------------------------------------------------------------------
  Ticket             | 11807
  Created By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Kolab backend: Parsing is a memory hog
  Queue              | Turba
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2012-12-03 18:08) wrote:

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