>PMFJI but what is the most simple way to determine number of hits an ASP.NET application gets? Is it in the application code or you can find out from IIS? TIA.

You can look at the IIS application logs, but you need some good filtering to get reliable data. There's a lot of content that IIS serves through ASP.NET (anything that hits a module or a handler basically).

I use in application logging if want to figure things like this out and log every ASP.NET request. The overhead for this - except for storage usage - is pretty minimal. In my West wind tools I use a simple log manager.

From Westwind.Utilities:

https://github.com/RickStrahl/WestwindToolkit/tree/master/Westwind.Utilities

LogManager Class docs:
http://west-wind.com/westwindtoolkit/docs?page=_2mp013ssr.htm

From there you can either use the sample forms we provide or query the database yourself.

+++ Rick ---

>
>>250,000 backend hits a day is a nice load, but I wouldn't call that heavy by any means.
>>
>>I run 10 different ASP.NET apps on my server 3 of which generate on average 500,000 backend hits a day and much more during peaks, and the server isn't even sweating over this load. And this is on 6 year old albeit reasonably powerful machine (Quadcore, multiple drives for OS/data)...
>>
>>With customers I routinely run apps that are running multiple millions of hits a day on a single moderately configured box... for light loads getting several hundred requests a second is not unheard of with IIS and ASP.NET.
>>
>>But, a lot depends on what you're doing in your backend hits. 20-25 database hits is a lot, but ultimately what matters is how long do requests take and what CPU impact do they have. You should be able to monitor CPU load which is usually a good indicator of whether your server is on its way to overload. Generally when load consistently spikes over 50% it's time to think about more hardware or load balancing of some sort.
>>
>>Luckily load balancing with IIS is pretty easy these days with Application Request Routing which is a built-in IIS load balancer that is easy to use and actually is pretty efficient. So there are fairly easy scalability options available.
>>
>>+++ Rick ---
>>
>>
>>
>>>I have a box which is approaching a quarter million hits per day. That means an average of 3 hits per second on a daily basis. The response time of the site is still almost immediate and we can increase the load by much more.
>>>
>>>The average number of SQL hits per hit is about 20 to 25. We have about 5 million hits to SQL Server on a daily basis.
>>>
>>>I think I remember a few years ago someone who mentioned that over 200,000 hits, there isn't much server configuration that would be able to handle much. Then would be the time to start DNS server routing for IIS and so on.
>>>
>>>I am pretty confident that I can reach half a million hits per day on the same server without having to start spreading it.
>>>
>>>Any of you would like to share your metrix for comparism as this would be valuable information to collect?