[horde] Horde Implementation Going South

[Dave Cunningham]

Sorry...  do NEED, not 'do not'.

Dave


-----Original Message-----
From: horde-bounces at lists.horde.org on behalf of Dave Cunningham
Sent: Wed 9/5/2007 12:03 PM
To: Chuck Hagenbuch; horde at lists.horde.org
Subject: Re: [horde] Horde Implementation Going South
 

Sadly, we do not the sharing features.  Although, with the way things are going, I may take your advice and disable this feature temporarily until we can come up with a better solution.

Someone else had mentioned 3.2.x.  But, sadly, we have just implemented this version and 3.2.x includes many visual and functional differences that would make it hard to upgrade.  So, we're hoping we can fix the issues we have with 3.1.4.

Thanks for the tip.

Dave

-----Original Message-----
From: horde-bounces at lists.horde.org on behalf of Chuck Hagenbuch
Sent: Wed 9/5/2007 11:58 AM
To: horde at lists.horde.org
Subject: Re: [horde] Horde Implementation Going South
 
Quoting Dave Cunningham <dcunningham at meccorp.mec.edu>:

> 1.) Sometimes a single Apache process quickly builds up and eats 30,  
> 40 or even 50% of the ram on the system.  Sometimes this process  
> finishes.  Other times, especially if the overall system load is  
> already high, it simply hangs and eventually brings down the entire  
> web server.  I then have to kill and restart apache.  I have tried  
> tweaking httpd, following the performance suggestions provided with  
> the horde documentation.  Keepalives are on and the number of  
> threads is high.
>
> 2.) MYSQL - We have mysql running on a separate server of the same  
> specs.  It frequently uses 100% of BOTH cpus in what appears, by  
> using myTop, to be a bunch of Join statements on the horde_datatree  
> table. Switching to InnoDB seemed to make it faster at first.  But,  
> as the number of sessions increased, all performance increases were  
> lost and perhaps made worse.  I also tried upgrading mysql from the  
> stock RHEL4 version 4 rpm to the V5 RPM from mysql.org.  There was  
> no noticeable difference there.

Both of these problems sound like they have one source - datatree  
queries. Horde 3.2 has some improvements here; for one thing you can  
prevent users from sharing their calendars/tasklists/address  
books/etc. If you don't need shares, though, simply turning the  
datatree system off (move it from a sql driver to none) should resolve  
these problems for you.

-chuck
-- 
Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: horde-unsubscribe at lists.horde.org

-- 
Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: horde-unsubscribe at lists.horde.org