Hey Guys. I am doing some load testing on my site and keep getting a 503 error when I get about 50 users on the server. Everything is fine until about 45 users. Then I start getting 503 errors from the server, and everything stops working. I talked to the support guys, and they said it was probably one of the three conditions being met and recycled. Windows Server 2008/IIS 7: * Idle timeout set to 20 minutes. (Information is NOT logged) * Memory threshold set to 200 MB. * CPU limit set to 70% utilization over 300 seconds (5 minutes). Now is that 200MB total. For all 50 users???? If so, I bet that is the problem. I run a really intense database application. How can I tell how much memory each user is taking up. Thanks in advance, Chad
It's 200mb for your application pool, so yes. I'm not sure you can determine memory use per user - that would be difficult to determine when dealing with that many concurrent users. But maybe someone else has a way to get a ballpark reading. 45-50 users all doing the same thing at the same time is indicative of pretty heavy traffic, I'm sure you realize that. Real world usage patterns are rarely that concentrated. But if you have to support that many users (assuming there is something on the site aside from the database application, you're talking about thousands of concurrent visitors), you may have to consider dedicated hosting.