3 ms·
And I was proud of my API backend processing 70M requests a day... That's suddenly feeling like a lot less traffic and a lot less spectacular.
by themartorana 12y ago
And I was proud of my API backend processing 70M requests a day... That's suddenly feeling like a lot less traffic and a lot less spectacular.
- eugeneionesco 12y agoOn what hardware was that?
- themartorana 12y agoAWS, ~11 EC2 c1-medium boxes (auto scales), one db.r3.4xlarge RDS MySQL server, plus a beefy Redis server (instance size escapes me). FreeBSD 10 on the EC2 boxes, whatever Linux AWS is running on their managed service instances. Nginx backed by Python and Go servers. Plus a smattering of other services like ELBs, etc. I can't imagine having something so critical that you build a custom Nginx plugin. I thought I was cool for doing a bit of Lua scripting. :)
- avidas 12y agoHow were your monthly expenses like for this setup?
- themartorana 12y agoAlthough it's difficult to fully articulate, as our traffic is basically a bell curve through the day and we auto scale between say 7 and 13 servers throughout the day... We pay about $4200/month. That includes several TB of traffic (which we gzip compress where it makes sense).
- elcct 12y agoI was able to process about 250M requests a day on a dedicated server (E3) without breaking a sweat.
- ddorian43 12y agoIt depends on what you're doing in those requests. Ex: Realtime stats system. On each request doing several get,set,increment,push-into-queue, geoip + 1 bulk-postgresql-upsert every second. 1ms response, 400 requests/second, 3 python processes, 10$/month shared hosting.