ThinkGeo.com    |     Blog    |     Wiki    |     Support

Session state other than InProc makes the map incredibly slow

I’m trying to support a web farm, and it’s my understanding that you require a session state other than InProc for your map to work correctly. The problem is, that if i go to a server that isn’t in a web farm and simply change the sessionstate (I’ve tried both SQL (https://support.microsoft.com/en-us/help/317604/how-to-configure-sql-server-to-store-asp-net-session-state) and Redis ( https://www.nuget.org/packages/Microsoft.Web.RedisSessionStateProvider/ ) and both perform in the same way, incredibly slow. if i switch back to InProc, speeds right up, switch back it’s slow again.

All of the slowness is in loading the tile_GeoResource.axd files. When i say slow, i mean that this page that normally takes a few seconds to load can take up to 2 minutes instead.

Is this something you guys have seen before, or have guidelines on how to configure your session state servers?

Hi Thomas,

The Session State is not required in Web Form MapSuite. It will use default if you didn’t setting that. The Session State is InProc. Please refer https://msdn.microsoft.com/en-us/library/ms178586.aspx

We didn’t have any user report Redis SessionState issue, and we didn’t do the testing for the Redis SessionState, Can you give us one sample that we can do the testing Redis SessionState? we will do some testing for that.

Thanks
Mark

that is entirely the opposite of what your team has said in this issue here:


where you say explicitly that the session state CANNOT be InProc in a web farm/load balancing situation.

Redis is only an example, i’m getting exactly the same issue whether or not i use Redis or SQL. if it helps you, ignore that i said Redis and focus only on SQL session state being slow.

Hi Thomas,

Thanks for your information, we will do some testing based on SQLServer. If there is any updates, we will let you know that.

Thanks
Mark

Hi Thomas,

Mark misunderstand webfarm to webform in his first reply.

Just like we ever research result, the session mode cannot be InProc, because we cannot interfere the synchronization of webfarm. So the only solution to make your pages works well is save the session in a server.

The webfarm is very old tech and had stopped to upgrade after 2012, we even cannot install it again now. So if the slow problem is caused by webfarm itself, I think we cannot solve it. For make sure that we need you do a simple test in your side: Please use your same page without webfarm environment, you can make it work in a normal IIS and just save the session in same server, and then access it to compare the load speed. If the speed is the same slow, that should be the page and session problem, we can go on look into it and see how to solve it. If the speed is fast in this scenario, that means the problem is caused by webfarm, I think maybe you want to find another solution to replace webfarm.

Regards,

Ethan