Being into Django+AWS development at the moment (and using http://eucalyptus.cs.ucsb.edu/ for a private cloud with AWS as an extension as AWS is not cost effective in many ways), I find this a good article to improve performance in a basic way. Many people seem to forget not all content needs to be dynamic and some basic modification can seriously improve performance.
It is great to see articles that include code snippets and architecture diagrams. People should use direct example more often instead of trying to describe things in words.
Lastly, I'd suggest using nginx (http://wiki.codemongers.com/Main) as I found it to be a serious improvement on lighttp for many of my projects.
I've heard great things about nginx. In relation to this article, how would you implement the lua script presented in this article with nginx? I know that Perl can be embedded in the server, but I'm not sure if that would be the proper solution for deciding which files to serve statically and which to serve dynamically at the httpserver level.
Comments
Being into Django+AWS development at the moment (and using http://eucalyptus.cs.ucsb.edu/ for a private cloud with AWS as an extension as AWS is not cost effective in many ways), I find this a good article to improve performance in a basic way. Many people seem to forget not all content needs to be dynamic and some basic modification can seriously improve performance.
It is great to see articles that include code snippets and architecture diagrams. People should use direct example more often instead of trying to describe things in words.
Lastly, I'd suggest using nginx (http://wiki.codemongers.com/Main) as I found it to be a serious improvement on lighttp for many of my projects.
I've heard great things about nginx. In relation to this article, how would you implement the lua script presented in this article with nginx? I know that Perl can be embedded in the server, but I'm not sure if that would be the proper solution for deciding which files to serve statically and which to serve dynamically at the httpserver level.
you probably don't need perl for that. afaics from the snippet, it fits into nginx mod_rewrite. maybe something like this:
if ($http_cookie ~* "auth=1" ) { proxy_pass http://backend ; break ; }
if (!-f $request_filename) { proxy_pass http://backend ; break ; }