[Tickets #1920] Trean extremely slow; probably due to amount of data transferred

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=1920
-----------------------------------------------------------------------
 Ticket             | 1920
 Updated By         | wk at mailstation.de
 Summary            | Trean extremely slow; probably due to amount of data transferred
 Queue              | Trean
 State              | Unconfirmed
 Priority           | 3. High
 Type               | Bug
 Owners             | Ben Chavet
+New Attachment     | trean_http_log.zip
-----------------------------------------------------------------------


wk at mailstation.de (2005-05-07 04:41) wrote:

Ok, I think I know why it transfers so much: Until now I didn't realize that
even if only part of the category tree is being *shown*, it's being
completely rebuilt including all its leafs, those not shown, too, on
virtually any action. 

On entering Trean: Would it be possible to build only those parts of the
tree that are shown? I realize that would mean you would have to load other
parts dynamically when the user uncollapses new leafs.

On entering a category: I don't really see why the whole category tree would
have to be rebuilt. What am I missing here?

I've attached a ZIP archive containing two logs of the http streams. One for
entering Trean, the other for opening a category.