Impact of session state read only in a web farm

Question

Recently to allow concurrent requests at some level and to increase the performance , we enabled EnableSessionState="Readonly" for one our .aspx page for read only access for session data.

I would like to know enabling this in web farm, will this effect any data loose or any other impact in server or user ?

Current Web Farm Settings:

Lets say We have 4 servers.

1. Lets say User A, requests for the page http://example.com/StudentDetails.aspx , this request hits Load Balancer.

2. Load Balancer based on traffic transfer the request to any 1 from 4 avialable servers.

3. Each server Has InProc Session State mode enabled.

4. We ensure that the same server handles subsequent requests from the same client.

Any help would be great.

Answer 1

What impact have you anticipated?

You simply set it read only in one single page. If, as you mentioned, you aren't even sharing sessions between your servers, then effectively for session purposes you don't even have a farm. You just have 4 individual servers. There's no impact on the farm because there's no session sharing.

If you do start sharing sessions as I suggested in the comments, then I still think the impact will be minimal if any at all. Read-only access should lead to less blocking (eg as might occur if the user is requesting two session-enabled pages concurrently) but that's all.