[Systems] Discovery One load balancing testing

Aleksey Lim alsroot at member.fsf.org
Wed Dec 2 15:44:36 EST 2009

On Wed, Dec 02, 2009 at 02:27:23PM -0600, dfarning at sugarlabs.org wrote:
> It looks like it is time to enter a feature freeze on Discovery One and spend some time debugging and tuning.
> Recent Features:
> Log parser - Yesterday alsroot moved the log parser from sunjammer(acting as a web node) to aslo-proxy.  Our download count has been under recording for the past couple of weeks.  By parsing the squid logs we can catch everthing.

I guess we can disable apache logs to /srv/www-sugarlabs/activities on

> Awstats - Yesterday we moved an awstats instance to aslo-proxy to help us get a better sense of the actual aslo traffic.  The awstats instance on sunjammer gave us information about total traffic on sunjammer. 
> HAproxy - This morning we enabled HAproxy on aslo-proxy so we can load balance across multiple web-node.
> Stress testing - I am currently stress testing the new stack with siege.  Sunjammer is still in production.  To prevent interference with normal aslo users, the LB is sending 90% of the requests to aslo-web and only 10% of the requests to sunjammer.
> It is pretty cool to be able to kill apache on aslo-web and have the benchmark keep running -- albeit much slower.  On the other hand, we need to run siege from a different machine.  We are using a quarter of treehouse's total cpu just to run siege.
> david 


More information about the Systems mailing list