[horde] Horde Problems Getting Better, but MYSQL still an issue

[Jan Schneider]

Zitat von Dave Cunningham <dcunningham at meccorp.mec.edu>:

>
> My mysql database just gets thoroughly pinned.  I've tried a bunch  
> of things mentioned so far on this list, but nothing seems to have  
> solved the problem yet.  The mysql process still shows a failry  
> consistant 150 to 200% CPU (dual cpu) usage in top.
>
> I have tried converting to InnoDB to allow row locking.  But, I'm  
> wondering if I have to do something else to get my queries to lock  
> rows rather than whole tables.  Is this something that mysql figures  
> out on it's own, or is it something I have to set or edit in the  
> queries?  I would think the indexes should help it figure out to  
> only lock certain rows, but things have not improved much with  
> tweaking.
>
> I have two implementations of horde.  One server has one instance of  
> horde running on it, with about 1000-1500 active sessions.  This one  
> horde instance has one database for all 1500 sessions.  I have a  
> second server that has about 2 dozen virtual hosts, each running a  
> separate instance of horde.  Each instance has it's own database.   
> The total usage is again around 1000-1500 sessions.  However, the  
> load on the database server is WAY smaller (about 1/8 -1/4 of the  
> CPU usage).  I figure this is because the various aspects of the  
> datatree are split for each instance over many databases.  So, each  
> datatree join is FAR smaller than the single implementation.  Anyone  
> agree, disagree, or better, have a solution to help?

That sounds correct, and you should even see it from the  
horde_datatree table sizes.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/