Closed lizadaly closed 7 years ago
Set up some concurrency tests with Blazemeter. AWS seems to keep up spawning new app servers as the load goes up; site seemed to be totally OK getting hammered with 500 concurrent users over a 20 minute period.
Response time creeps up until a new app server is spawned and then drops back down:
During times of peak demand users can expect to get a few 503 errors until new app servers come on board, but this can be easily ameliorated by proactively provisioning more than we'd normally want (like right after a public announcement).
Would like to ensure that the site won't fall over during a public beta review period.