EnableSessionState = ReadOnly - Possible Side Effects?

Question

We have a fairly large web solution that runs on .Net 4.5. Recently, when we were considering a performance problem, when the system seemed to be serving only one request at any given time (per client), we learned that the reason for this was the session state. By changing the EnableSessionState attribute to ReadOnly, you can serve multiple requests at the same time, and performance has improved significantly.

We thought that we might face all the problems, since we rely on the state of the session for a number of things in our system, but so far we really have not had any negative side effects. Logins work as expected, and all the things that we keep in session state also work fine.

This begs the question ... why is this not the default behavior? Are there any obvious bad side effects that we have not experienced yet?

Answer 1

Still only 62 views?

It’s good that we started it now for about 7 months without any bad side effects, only the performance has improved significantly. Therefore, the Answer to my question: "I do not know and no."

Forward :-)

Answer 2

Sessions for Readonly were recently established, and initially this accelerated the response of the page, we noticed that any long messages, such as a long report from another session, will start the resources of the entire site, blocking everyone. Our solution was to queue any heavy reporting processes onto the reporting engine and allow web focus on the pages.

However, with the end of the session, he can better allocate CPU cycles to each session and bear the brunt of another heavy session. That was our observation.