Currently we have a domain name registered with an ISP that points to an Amazon EC2 instance with an Elastic IP. This instance is running IIS hosting a simple ASP.NET site that URL forwards visitors to two external sites via round-robin.

This EC2 instance is a Windows Large and is costing us about $350ish dollars a month. I think this is a really bad solution URL forwarding/Load balancing solution.

I think what we need is a micro EC2 instance running HAProxy that will do our URL redirects and load balancing. Given that the number of users using the service is less than 5000 and the number of daily connections will be less than 10,000.

However I do not want to create bottleneck by choosing too small an instance type.

How can I test the HAProxy setup to determine the number of connections it can comfortably manage?



You should perform stress testing using one of load testing tools. I recommend using siege, JMeter or Tsung. siege is the simplest one and it should suit your needs since you don't need complex testing scenarios.

  • Thanks siege looks interesting I think I will give that a go. – Joe T Feb 9 '11 at 8:54

Can I ask, have you ever performed any benchmarks on your Large Instance without any of the IIS redirecting/round robin in front of it? You may not even have a load issue, or not where you think it is.

Secondly, if you do need a load balancer, I'd recommend looking into Amazon's Elastic Load Balancing service to take away some of the guesswork of right-sizing your instance for HAProxy.

  • The question states the sites are external so cannot use ELB from AWS. Also the driver behind the change is cost, not a load bottleneck. – Joe T Feb 9 '11 at 8:55
  • You're right: should've clarified that first. – gravyface Feb 9 '11 at 14:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.