[horde] horde_datatree grows larger

[Kevin Myer]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Serhat Gungor <gungorserh at itu.edu.tr>:
>
>> I am using horde framework 3, imp 4 and also turba, kronolith, mnemo and
>> nag. I am using horde datatree system storage SQL. My horde_datatree tables
>> become larger because of my large number of users. It has aproximately
>> 270,000 rows. Because of this horde slows down.

This relates to a question I've been meaning to ask for some time.  Its 
noted in
the documentation that the DataTree can grow quite large and slow down a
system.  My question is this:  is there a reasonable set of maintenance
procedures that can be done to safely prune elements from a DataTree?  For
example, over time, you accumulate shares for users whose accounts have been
deleted.  So horde_datatree grows, and horde_datatree_attributes grows, 
but may
contain a lot of dead trees.  Also, I find the IMP message history to be very
helpful and that kind of functionality is in a lot of modern mail 
clients.  But
it would also be possible to do something like, say after six months, delete
the IMP message history (in much the same way that a maintenance script 
for IMP
runs to delete linked attachments older than six months).

The bottom line is the DataTree can grow without bounds, which means planning
backends appropriately.  But are there ways to stem that tide a bit, 
and remove
truly unneeded or items that are meaningless after a time?  This has to be
considered because there will be large sites that end up with hundreds of
thousands or millions of DataTree entries, and culling the unneccessary or
entries of deleted users would be a good thing.

Kevin



-- 
Kevin M. Myer
Senior Systems Administrator
Lancaster-Lebanon Intermediate Unit 13  http://www.iu13.org