Hi folks,

I'm noticing that with just a little bit of activity on mongrel2 with ssl, the 
server will start hogging an unreasonable amount of cpu and stay that way for 
awhile. This doesn't seem to affect non-ssl. I have two mongrel2 processes, one 
for each type, and I can bombard the non-ssl one with traffic and things work 
as 
expected (small cpu spike, then 0%).

Is this a known issue, and is there a known fix? I'd love any tips here. I'm 
running this on a production service and this is a big problem, so I'm about 
to go hacking on mongrel2's code today.

As a bandage I'm restarting the ssl process every five minutes with cron.

Thanks,
Justin

Reply via email to