Lessons learned tuning TCP and Nginx in EC2

“Our average traffic at Chartbeat has grown about 33% over the last year and depending on news events, we can see our traffic jump 33% or more in a single day. Recently we’ve begun investigating ways we can improve performance for handling this traffic through our systems. We set out and collected additional metrics from our systems and we were able to reduce TCP retry timeouts, reduce CPU usage across our front end machines by about 20%, and improve our average response time from 175ms to 30ms…”

Part 1: Lessons learned tuning TCP and Nginx in EC2

“In part 1 of our post, one of the items we discussed was our issues with using DNS as a load balancing solution. To recap, at the end of our last post we were still setup with Dyn’s load balancing solution and our servers were receiving a disproportionate amount traffic to them. Server failures were still not as seamless as we wanted, due to the issues with DNS TTLs not always being obeyed and our response times were a lot higher than we wanted them to be, hovering around 200-250ms…”

Part 2: Lessons learned tuning TCP and Nginx in EC2