So this is a bit of old news but I have been slack on my write up. A new version of FAWPS (I am trying to get William to call it Frisky) which is 0.2. He even gave me credit for helping with some of the C coding. I must admit the little I did to get him started was nothing to brag about that is for sure. However we had a good email exchange and I think we both learned a lot from working on this release. Learning GIT was a challenge but now that I almost know what I am doing it is so much better a source management tool than any other I have used. That Linus guy wrote this in 2 weeks, what an uber hack.
Anyway the new version of FAWPS is a pretty darn innovative implementation. William wrapped the libevent httpd server using Python. As much fun as hacking apache (or lighttpd) rule are (not), I have been having fun playing around with doing more dynamic things with static content serving. Even with a bit Python code I can still get 2K req/sec. It is amazing the amount of flexibility that is enabled because of this. Site skins based on domain is one thing I have noticed. The templates don't need to generate link to the css that are something like "/css/1/mycss.css" they can be just "/css/mycss.css" because based on the domain FAWPS is so fast it doesn't matter.
Where to go from here? Well there are so many little server application I would like to write with this kind of performance. I have started to work on a static file server that is cluster aware. One of the problems for large sites is when there is a cluster of machines serving up content the new or updated files have to get distributed across the cluster. More on this project later.
0 comments:
Post a Comment