Thoughts on live chat 
Sign up | Plans | Help | Contact
Tags


Filed under

cache

 
July 23, 2008

Faster Customization Changes

We’ve been getting a lot of feedback on hab.la recently and we noticed that many of you thought customization was broken. Customization was working, but had a bit of lag due to some very aggressive (and somewhat poorly designed) caching.

I just pushed out a set of changes to the site that will make customization changes take affect instantly :-).

This fix should also fix the problem where the “One more step to go” message gets shown even after the first step was complete. Only the site operator would see this message, but I am sure it made things seem like they were messed up.

For those of you new to Hab.la, you can customize the messages shown in the Hab.la window as well as the colors and positioning of the Hab.la window in the customize section of your My Hab.la page.

There are a lot of exciting things happening here at Hab.la. Kevin should be blogging about some of his contributions to the excitement soon :-)

Filed under  //   backend   cache   memcache   rpc  

Comments [0]

October 17, 2007

As lighttpd as a feather as quick as a wink

Ok, that title was pretty lame. I digress.

Here’s the news: we’ve migrated hab.la’s front end proxy servers on to lighttpd so now we have joined the in crowd for web2.0 applications (delicious .. anyone who does ruby …etc ). As an end user you should see a general speed increase for most aspects of hab.la. However, this migration was done to specifically address some of the problems apache experiences when dealing with large number of passive connections. [Jeremy Zawodny has a great post on dealing with slow HTTP clients – which is very similar to what hab.la appears to be from the proxy server point of view at http://jeremy.zawodny.com/blog/archives/008496.html. You might want to also read about cache performance issues http://www.mnot.net/blog/2006/08/21/caching_performance ]

Ideally we should remove the proxy server from the mix and you should hit the RPC server directly, either by running the RPC server on port 80 (requires root) or by some sort of TCP level routing trick to tunnel requests around from port 80 to port 8000. But, that’s a fix for another day.

Filed under  //   apache   backend   cache   lighttpd   optimization   performance   proxy   slow   speed   tuning  

Comments [0]