的EnableSessionState =只读 - 可能的副作用？ [英] EnableSessionState = ReadOnly - possible side effects?

问题描述

我们必须运行在净4​​.5相当大的基于Web的解决方案。最近，当我们检查的性能问题，其中该系统似乎只提供在任何给定时间一个请求（每个客户端），我们得知的，该原因是会话状态。通过改变的EnableSessionState属性为ReadOnly，多个请求可以同时服务和性能显着改善。

We have a fairly big web based solution which runs on .Net 4.5. Recently, while we were examining a performance issue where the system seemed to be only serving one request at any given time (per client) we learned that the cause of that was the session state. By changing the EnableSessionState attribute to ReadOnly, multiple requests can be served simultaneously and performance was dramatically improved.

我们想，也许我们会遇到各种各样的问题，因为我们是依靠会话状态的一些东西在我们的系统中，但到目前为止，我们还没有真正有任何负面影响都没有。登录如预期而我们存储在会话状态的东西似乎也工作正常工作。

We thought maybe that we would run into all kinds of issues since we are relying on the session state for a number of things in our system, but so far we haven't really had any negative side effects at all. Logins work as expected and all the things we store in the session state also seem to work fine.

这引出了一个问题......为什么不是这样的默认行为？是否有此任何明显的不良副作用，我们只是还没有经历过没有？

That begs the question ... why isn't this the default behaviour? Are there any obvious bad side effects of this that we just have not experienced yet?

推荐答案

不过只有62次？

好了，我们已经没有不良副作用，不仅大大提高了性能运行现在这样大约7个月。所以，回答我的问题是：我不知道，也没有。

Well we've been running this now for about 7 months with no bad side effects, only greatly improved performance. So The answer to my question is "I do not know and no".

来吧： - ）

这篇关于的EnableSessionState =只读 - 可能的副作用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！