Thoughts on live chat 
Sign up free | Pricing | Tour | About | Contact
Contributors
Tags


Filed under

performance

 
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  
Posted by Olark 

Comments [0]

April 25, 2007
 

Inexorable march of progress

The big update for today is opening the Jabber client when a user visits the page, rather than opening it when the user opens a chat box. The advantages boil down to:

  • This greatly simplifies the process of identifying whether an operator is available.
  • Operators can initiate chat with web users.
  • Uhhm .. that's all I've got.

At some point we may want to add some kind of privacy control for web users who do not want operators to initiate chat. Maybe we could have some kind of cookie that prevents hab.la from opening the Jabber session unless you specifically ask it to.

Also, all these Jabber streams may cause a performance issue at some point, but I guess we'll cross that bridge when we come to it.

Filed under  //   performance   privacy   rpc   server  
Posted by Olark 

Comments [0]

April 25, 2007
 

Inexorable march of progress

The big update for today is opening the Jabber client when a user visits the page, rather than opening it when the user opens a chat box. The advantages boil down to:

  • This greatly simplifies the process of identifying whether an operator is available.
  • Operators can initiate chat with web users.
  • Uhhm .. that's all I've got.

At some point we may want to add some kind of privacy control for web users who do not want operators to initiate chat. Maybe we could have some kind of cookie that prevents hab.la from opening the Jabber session unless you specifically ask it to.

Also, all these Jabber streams may cause a performance issue at some point, but I guess we'll cross that bridge when we come to it.

Filed under  //   performance   privacy   rpc   server  
Posted by Olark 

Comments [0]