All geek questions in one place

What do ASP.NET performance counters mean?

I'm trying to better understand how streams work in ASP.NET, so I have a test site with several pages, and I have a WinForms test client that creates 40 approximately parallel requests to a test site. Requests take about 5-10 seconds to complete — they call the web service on another server. When I start the test client, I can use Fiddler to see that requests are being executed at the same time. However, when I look at Performance Monitor on a web server, with the counters "ASP.NET Apps v2.0.xxx/Requests Executing", "ASP.NET/Requests Current", "Queens Requests Queued", these counters never display again 2. This is so, regardless of whether the test page I request is configured using Async = True and using the Start / End templatecall the web service or if it is configured to synchronously call. Judging by what I see in Fiddler, I think I should see 40 queries in one of these states, but I do not. Why is this? Don't these counters mean what I mean?

+3
source share
1 answer

If requests go to the same server, this can lead to restriction of access to the System.Net system and processing of only two connections at a time.

This stack overflow question shows an example of changes to web.config to enable additional connections.

0
source

Source: https://habr.com/ru/post/1760757/

More articles:


All Articles