I just discovered that every request in an ASP.Net web application gets a Session lock at the beginning of a request, and then releases it at the end of the request!
I have a string buffer of about 2000 characters and need to check the buffer if it contains a specific string.
Will do the check in a ASP.NET 2.0 webapp for every webrequest.
I am trying to improve performance of my web portal. I’m using Session to store state information.
Given the chart here, what should I be looking at to identify the bottleneck? As you can see, requests are averaging nearly 14 seconds under load and the bulk of that time is attributed to the CLR in New Relic’s profiling data. In the performance breakdown for a particular page, it attributes the bulk of the time to the WebTransaction/.aspx page.
What are the ways by which we can reduce the size of the HTML Response sent by an asp.net application?
I found some wild remarks that ASP.NET MVC is 30x faster than ASP.NET WebForms. What real performance difference is there, has this been measured and what are the performance benefits.
Every now and then (always after a long period of idle-time, e.g. overnight) when I access a site built using asp.net – it takes around 15 seconds to load the page (15 seconds before I see any progress whatsoever, then the page comes up fast).
OK, here is the question, I have a asp.net website, there is an aspx page called GetThumbnail.aspx, the code is like below:
After IIS reset, first hit taking a long time because AppPool is starting and other .NET components, DB connections are initializing.
I have various servers (dev, 2 x test, 2 x prod) running the same asp.net site.