3 ms·
300 active users is hardly any-- but keep in mind my product had a very active API and a browser plugin (which was basically a Rails view in an iframe) that use
by mortallywounded 3y ago
300 active users is hardly any-- but keep in mind my product had a very active API and a browser plugin (which was basically a Rails view in an iframe) that users used often. A single user could easily hit the server hundreds (or thousands) of times in a minute.
- pmontra 3y agoOk, so it's not the typical Rails app. I was thinking about something with long CPU bound operations inside the controller or in background but a lot of hits per user is like having to serve at least 100 times more users.