[horde] Horde 3.1.3 and datatree related performance problems

[Chuck Hagenbuch]

Quoting Chris Stromsoe <cbs at cts.ucla.edu>:

> I have partially fixed the kronolith problems.  I've added two  
> indexes which have cut query time down significantly.
>
> 1) There is no index created for horde_datatree(datatree_id).  I  
> added one and cut one set of queries from ~30s down to .5s:

Really? I thought PRIMARY KEY would automatically create an index.  
That's not true?

> 2) There is a (default) BTREE index for  
> horde_datatree_attributes(datatree_id), but the postgresql query  
> planner was electing not to use it whenever there were more than 500  
> to 600 items in the IN(*) collection.  I added a hash index and cut  
> another set of queries from 5m - 6m down to 10s or 11s:
>
> CREATE INDEX datatree_attribute_id_idx ON horde_datatree_attributes  
> USING hash(datatree_id);

I'll add that to a pgsql-specific datatree sql definition after the  
first point is clarified, thanks.

> Calls to listCalendars() with $ownersonly = false take forever to  
> complete; loading calendars.php takes more than 20 minutes.   
> Changing listCalendars() to force $ownersonly = true fixes the  
> performance problem, but I suspect won't be a very useful solution.
>
> Any ideas about where to look to speed things up?

Probably back to the datatree code again, perhaps in the creation of  
large arrays.

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris