Developer forum

Forum » Development » Slow responsetim

Slow responsetim

Martin Grønbekk Moen
Reply

I have installed a montotoring system called "New Relic" in one of our solutions.
The response time is generally good, but I do get a fair amount of messages saying there are some slow performance on the website.

When I look furtger into this I see that the most time consuming page is deafult.aspx, and this is understandable since most of the traffic on a DW site runs through this page.
http://screencast.com/t/xXQ96X47IDX

When I look further into one (of many) request traces I find that the reason for the long response time is the segment called "AcquireRequestState"
http://screencast.com/t/GB0GXW2eLCT

I research more into this and find the following posts.
http://forums.asp.net/t/2090251.aspx?Slow+AcquireRequestState
http://stackoverflow.com/questions/3629709/i-just-discovered-why-all-asp-net-websites-are-slow-and-i-am-trying-to-work-out
https://forums.iis.net/t/1169137.aspx

Basically it is said that it is due to sessions and when a session is released.
Do anyone of you experience the same?

And what implications would it have to the DW solution to set:
<% @Page EnableSessionState="ReadOnly" %>

Any input is greatly appreciated :)


Replies

 
Nicolai Høeg Pedersen
Reply

I do not know much about AcquireRequestState, but looking at your screendumps, I think there are some requests that have been "stuck" in that state. As I recall there was a bug in IIS/.NET at some point regarding this

Since all of Dynamicweb frontend is Default.aspx, setting ReadOnly sessionstate would just mean that everything requiring sessions (login, cart etc) will not work.

You might be able to replace asp.net session module: https://github.com/dermeister0/LockFreeSessionState

AcquireRequestState

 

You must be logged in to post in the forum