Home/ Questions/Q 7435447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T10:04:35+00:00

I’m using JMeter for load testing. I’m going through and exercise of finding the

  • 0

I’m using JMeter for load testing. I’m going through and exercise of finding the max number of concurrent threads (users) that our webserver can handle by simply increasing the # of threads in my distributed JMeter test case, and firing off the test.

Then — it struck me, that while the MAX number may be useful, the REAL number of users that my website actually handles on average is the number I need to make the test fruitful.

Here are a few pieces of information about our setup:

  • This is a mixed .NET/Classic ASP site. Upon login, a browser session (with timeout) is created in both for the users.
  • Each session times out after 60 minutes.

Is there a way using this information, IIS logs, performance counters, and/or some calculation that will help me determine the average # of concurrent users we handle on our production site?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I can see a couple options here.

    1. Use Performance Monitor to get the current numbers or have it log all day and get an average. ASP.NET has a Requests Current counter. According to this page Classic ASP also has a Requests current, but I’ve never used it myself.

    2. Run the IIS logs through Log Parser to get the total number of requests and how long each took. I’m thinking that if you know how many requests come in each hour and how long each took, you can get an average of how many were running concurrently.

    Also, keep in mind that concurrent users isn’t quite the same as concurrent threads on the server. For one, multiple threads will be active per user while content like images is being downloaded. And after that the user will be on the page for a few minutes while the server is idle.

    • 0