Hi Guys, I know this is slightly off topic, but it''d be great to get some feedback from anyone who''s using mod_proxy on Apache 2.2 to redircet to a rails app on mongrel. Everything has been running fine generally but a few days back we started getting a gap in the performance between the Apache port and the mongrel port. accessing through port 80 was averaging ten times longer to serve 1000 requests compared to accessing mongrel directly throught port 8000. This is weird because essentially nothing had changed configuration wise and the number of requests being handled was fairly stable. So I gave Apache and then the server a reboot, but the problem still persisted. Came back after the weekend and everything seems ok but I''m very suspicious of problems that magically fix themselves. If anyone has any ideas of possible causes I''d be grateful or If you could share your Apache configuration for performance (I''m using pretty close to the defaults) as I wouldn''t mind squashing this before it resurfaces. Thanks -- Ross Riley riley.ross at gmail.com
On 03/07/06, Ross Riley <riley.ross at gmail.com> wrote:> Hi Guys, > I know this is slightly off topic, but it''d be great to get some > feedback from anyone who''s using mod_proxy on Apache 2.2 to redircet > to a rails app on mongrel.I''m happily using mod_proxy (not balancer) with Apache 2.0 to serve a couple of Rails apps with Mongrel, and not noticed any performance issues like those you describe, however I''m not particularly stressing my apps either. Mine is a fairly stock configuration as well, although I''m using mod_rewrite and mod_deflate in addition to mod_proxy.