Hi Jason,

On May 19, 2006, at 7:21 PM, Jason Hoffman wrote:
>
> # Redirect all non-static requests to cluster
>    RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
>    RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI}
> [P,QSA,L]
> part for what you're asking for and Bradley's correct, that will work
> fine for you.

I should have highlighted that part! Thanks for pointing it out.

> That's a nice elegant two line config for that (nice
> work bradley).

Thanks!

>
> We tend to stick to only proxying rather than rewriting and while you
> can do
>
> ProxyPass /favicon.ico !
>
> There isn't any respect for a wildcard there in the proxy pass
> directive.

There's definitely a trade off of performance for configuration  
simplicity/maintainability. The rewrites certainly have a negative  
impact on performance, but the ability to "config and forget" is  
pretty appealing for a lot of deployments.  If you don't use Rails  
page caching and you don't mind occasionally adding additional  
ProxyPass directives for application specific assets, then proxying  
is the way to go. Modifying the Apache conf to add a file_column or  
reloading a new conf to support Capistrano's disable_web is kind of a  
drag (and an annoyance for automated deployment/configuration).

I'm hoping to find a better balance between the two approaches than  
what I wrote up, but need to spend more time with httperf (and a big  
jug of corn whiskey).  I imagine the answer is dependent on the  
maturity of one's application,  comfort level with sysadmin stuff,  
and need to support 2000 requests/sec or 2000 requests/week!  It  
would be nice to have some good benchmarks on various deployments and  
graph the relationship between simplicity, features, and performance.  
Unfortunately, I tend to quickly loose productive development hours  
when I get sucked into the parallel universe that is httperf and  
Apache configuration tweaking.

What we, the Mongrel Nation, need is a front-end with the simplicity  
of Pound combined with Lighty's static performance, good caching  
support, and select Apache features . Seems like quite an opportunity  
for an enterprising C/C++ developer...

Regards,
Bradley Taylor

------
Rails Machine
Simplified Ruby on Rails application deployment
http://railsmachine.com




_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to