3 ms·
So let's assume thats $500 in dynos, that's approximately 14 dynos. You have 30k concurrent users per dyno using Node.JS? It's not that I don't believe you, I
by zeeg 14y ago
So let's assume thats $500 in dynos, that's approximately 14 dynos. You have 30k concurrent users per dyno using Node.JS?
It's not that I don't believe you, I just think you don't understand what you're saying.
(Actually, it is that I don't believe you)
That said, if this is if you're doing 500 requests/sec (that's very different than 500 concurrent users) per dyno, good for you. My main bottleneck was not so much CPU on the web machines (I hit memory limitations), but the database layer.
- benologist 14y agoJust over 20,000,000 people hit my API yesterday 700,749,252 times, playing the ~8,000 games my analytics platform is integrated in for a bit under 600 years in total play time. That's just yesterday. There are lots of different bottlenecks waiting for people operating at scale. Heroku and NodeJS, for my use case, eventually alleviated a whole bunch of them very cheaply.
- zeeg 14y ago>>> 20000000/24/60/60.0 ~231.46666666666667 requests a second?
- benologist 14y agoThat's people, not requests. :)
- zeeg 14y agoIs your graph showing concurrent (as in active connection) users?
- benologist 14y agoThe graph shows http requests, each individual person sends 'event.general...' requests approximately 2x per minute. In the last minute ~460,000 of those requests were made which means somewhere around 230,000 people sent data although there's room for that to be higher or lower depending on sessions starting, sessions ending, and just what period of time you want 'concurrent' to live within.
- deleted 14y ago[deleted]