It just happened again.  I had to restart apache twice.  At one point I saw 
135 apache processes running.  And heavy traffic that I think is coming 
from memcache, but I'm not sure.  Maybe I need to clear the cache?

--Steve


On Tuesday, September 10, 2013 8:09:39 AM UTC-7, Steve wrote:
>
> I know this is a shot in the dark, but I was hoping people with more 
> apache experience and better knowledge of RB might be able to give me some 
> pointers.  We're running RB 1.7.12 on a Centos6 box on a very beefy machine 
> which is dedicated to RB.  We're using MySQL and perforce and have close to 
> 900 users.  About twice a week (sometimes more) the load average on the 
> server spikes into the hundreds and the server becomes unresponsive.  The 
> only recourse is to stop apache, wait for the load average to come down and 
> then restart.  Sometimes when we restart, it spikes again immediately so we 
> typically pause for a bit and let the load average get down under 1 before 
> restarting.  When this happens, it looks like there a way more apache 
> processes running than there should be.  We're using the default settings 
> for apache on linux, which I believe limits the number of connections.  It 
> also looks like there's a lot of traffic going from apache to memcache, 
> which is running on the same machine.  
>
> I know this is not much to go on, but I was hoping someone who has 
> experience with fine-tuning RB on a linux server might give me some 
> pointers as to where to begin.
>
> Thanks
>
> --Steve
>
>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to