3 ms·
150 rpm is not that many. Assets, html, etc + backend calls - assuming the app won't make "out of the ordinary for a web app" calls (eg: against 1TB database, e
by czbond 12y ago
150 rpm is not that many. Assets, html, etc + backend calls - assuming the app won't make "out of the ordinary for a web app" calls (eg: against 1TB database, etc). You should ask about the behaviour of the 1,200 users (do they use it all at different times, all at burst periods, etc). Just throw it behind a load balancer, and I would think you'll be fine. I am used to Linux boxes, so check your RAM if that's enough.
- commn 12y agoMost of the 1200 use it at the same time. My webservers are behind the load balancer, but newrelic - the performance monitoring tool has lately started showing app server times taking as long as 1200ms. Rather than add more servers I wanted to hear from others if 2 instances for 1200 users is in the ballpark, or is my application poorly designed.