blocks|key|2430162|text|我建议不要使用会话状态，而不管提供程序是什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2430163|特别是您的“非常小的对象”使用viewstate。为什么？|2430164|最好的音阶。服务器上没什么好记的。|ordered-list-item|2430165|不用担心会话超时。|2430166|不用担心网络农场。|2430167|不要担心浪费掉的资源将永远不会回来。|2430168|特别是在ASP.NET+4中，viewstate可以非常容易管理和很小。|2430169|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

I would advise against the use of session state, regardless of the provider.

Especially with your "very small objects" use viewstate. Why?

<ol>
<li>Scales best of all. NOTHING to remember on the server.</li>
<li>NO worries about session timeout.</li>
<li>No worries about webfarms.</li>
<li>No worries about wasted resources for sessions that will never come back.</li>
</ol>

Especially in ASP.NET 4 viewstate can be very manageable and small.

blocks|key|875132|text|这取决于您所说的“缩放”会话存储是什么意思。如果您只讨论会话状态性能，则不会击败进程内会话状态提供程序。切换到Server提供程序实际上会使事情变得更慢--这是因为跨进程边界序列化和传输对象的额外开销。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|875133|Server可以帮助您扩展的地方是，它允许负载平衡的web场中的多台计算机共享单个会话状态。但是，它受到机器内存的限制，如果您将有大量并发会话，则可能需要使用SQL会话状态提供程序。|875134|对于web场中的大多数性能，您还可以尝试使用前面建议的AppFabric。我没有亲自做过，但它是在这里解释。|offset|length|875135|另外，这里有一个使用Memcached作为会话状态提供程序的链接。再说一次，我没有用过它，所以我不能对它提出意见.|875136|编辑:正如@HOCA在评论中提到的，如果成本不是问题，就有第三方解决方案。我听说过(但没有使用)的一个例子是ScaleOut+SessionServer。|875137|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ee790859.aspx|1|http://memcachedproviders.codeplex.com/|2|http://www.scaleoutsoftware.com/products/scaleout-sessionserver/^0|0|0|1C|6|0|0|0|W|1|0|1I|M|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@$F|10|G|11|1|12]]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$F|14|G|15|1|16]]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@$F|18|G|19|1|1A]]|A|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]]]

It depends on what you mean by "scaling" session storage. If your simply talking about session state performance, your not going to beat the in-process session state provider. Switching to the State Server provider will actually make things slower -- due to the extra overhead of serializing and transferring objects across process boundaries.

Where the State Server can help you scale, is that it allows multiple machines in a load balanced web-farm to share a single session state. It is limited by machine memory, however, and if you will have lots of concurrent sessions you may want to use the SQL Session State provider.

For the most performance in a web farm, you can also try using AppFabric as was previously suggested. I haven't done it myself but it is <a href="http://msdn.microsoft.com/en-us/library/ee790859.aspx" rel="nofollow">explained here.</a>

<a href="http://memcachedproviders.codeplex.com/" rel="nofollow">Also, here's a link for using Memcached as a Session State provider</a>. Again, I haven't used it, so I can't offer an opinion on it...

EDIT: As @HOCA mentions in the comments, there are 3rd party solutions if cost isn't an issue. One I've heard of (but not used) is <a href="http://www.scaleoutsoftware.com/products/scaleout-sessionserver/" rel="nofollow">ScaleOut SessionServer</a>.

blocks|key|2430254|text|我提供了一些链接，您可以在使用状态服务器正确缩放会话时阅读这些链接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2430255|来自Maarten+Balliauw博客的有用链接：|2430256|州%2529.aspx|unordered-list-item|offset|length|2430257|http://blog.maartenballiauw.be/post/2008/01/ASPNET-Session-State-Partitioning.aspx|2430258|http://blog.maartenballiauw.be/post/2008/01/ASPNET-Session-State-Partitioning-using-State-Server-Load-Balancing.aspx|2430259|与我国服务器有关的项目：|2430260|http://www.codeproject.com/KB/aspnet/p2pstateserver.aspx+(https://github.com/tenor/p2pStateServer的最新代码)|2430261|http://www.codeproject.com/KB/aspnet/stateserverfailover.aspx|2430262|希望这能有所帮助。|2430263|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.maartenballiauw.be/post/2007/11/ASPNET-load-balancing-and-ASPNET-state-server-%2528aspnet_state%2529.aspx|1|2|3|http://www.codeproject.com/KB/aspnet/p2pstateserver.aspx|4|https://github.com/tenor/p2pStateServer|5^0|0|0|0|9|0|0|0|2A|1|0|0|38|2|0|0|0|1K|3|1M|13|4|0|0|1P|5|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@$G|1C|H|1D|1|1E]]|A|$]]|$1|I|3|J|5|F|7|1F|8|@]|9|@$G|1G|H|1H|1|1I]]|A|$]]|$1|K|3|L|5|F|7|1J|8|@]|9|@$G|1K|H|1L|1|1M]]|A|$]]|$1|M|3|N|5|6|7|1N|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1O|8|@]|9|@$G|1P|H|1Q|1|1R]|$G|1S|H|1T|1|1U]]|A|$]]|$1|Q|3|R|5|F|7|1V|8|@]|9|@$G|1W|H|1X|1|1Y]]|A|$]]|$1|S|3|T|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|J]]|13|$5|X|Y|Z|A|$10|L]]|14|$5|X|Y|Z|A|$10|15]]|16|$5|X|Y|Z|A|$10|17]]|18|$5|X|Y|Z|A|$10|R]]]]

I've provided some links you can read up on on properly scaling session using the state server.

Useful links from Maarten Balliauw's blog:

<ul>
<li><a href="http://blog.maartenballiauw.be/post/2007/11/ASPNET-load-balancing-and-ASPNET-state-server-%28aspnet_state%29.aspx" rel="nofollow">http://blog.maartenballiauw.be/post/2007/11/ASPNET-load-balancing-and-ASPNET-state-server-%28aspnet_state%29.aspx</a></li>
<li><a href="http://blog.maartenballiauw.be/post/2008/01/ASPNET-Session-State-Partitioning.aspx" rel="nofollow">http://blog.maartenballiauw.be/post/2008/01/ASPNET-Session-State-Partitioning.aspx</a></li>
<li><a href="http://blog.maartenballiauw.be/post/2008/01/ASPNET-Session-State-Partitioning-using-State-Server-Load-Balancing.aspx" rel="nofollow">http://blog.maartenballiauw.be/post/2008/01/ASPNET-Session-State-Partitioning-using-State-Server-Load-Balancing.aspx</a></li>
</ul>

My State Server related projects:

<ul>
<li><a href="http://www.codeproject.com/KB/aspnet/p2pstateserver.aspx" rel="nofollow">http://www.codeproject.com/KB/aspnet/p2pstateserver.aspx</a> (latest code at <a href="https://github.com/tenor/p2pStateServer" rel="nofollow">https://github.com/tenor/p2pStateServer</a>)</li>
<li><a href="http://www.codeproject.com/KB/aspnet/stateserverfailover.aspx" rel="nofollow">http://www.codeproject.com/KB/aspnet/stateserverfailover.aspx</a></li>
</ul>

Hope that helps.

blocks|key|875213|text|我强烈建议，在开始扩展会话之前，首先要评估会话是否需要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|875214|无论页面是否使用该数据，每个页面加载的会话变量都会被序列化和反序列化。(编辑：Craig指出在.net+4+http://msdn.microsoft.com/en-us/library/system.web.sessionstate.sessionstatebehavior.aspx中对此有一定程度的控制，但这仍然存在缺陷，请参阅对此答案的评论。)|offset|length|style|BOLD|875215|对于单个服务器实例，这是可以的，因为您只是从web服务器的本地内存中提取它。这些应用程序的负载往往很小，因此在本地缓存用户特定信息是有意义的。|875216|但是，一旦将会话存储转移到另一台服务器，您就增加了应用程序的网络需求和页面加载时间。也就是说，每个页面都将导致会话数据从远程服务器、穿过网络线路移动到web服务器的内存中。|875217|此时，您必须扪心自问:是否每次从数据库服务器直接提取此信息的负载比每次从会话服务器中提取该信息更有必要？|875218|很少有需要时从数据库服务器中提取它的情况，或者比从远程会话服务器抓取它要花费更长的时间或带来更多的通信量。|875219|请记住，很多人将他们的数据库服务器设置为会话服务器，您将开始了解为什么使用会话没有任何意义。|875220|我只会考虑在负载平衡的web应用程序中使用会话，如果获取数据的时间超过了“合理”的时间。例如，如果您有一个非常复杂的查询要返回一个值，并且这个查询必须运行在很多页面上。但是即使这样，也有更好的方法可以降低处理远程会话数据的复杂性。|875221|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.sessionstate.sessionstatebehavior.aspx^0|0|10|2|1I|2H|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@$D|15|E|16|1|17]]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1C|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

I would highly recommend that before you look in to scaling out session that you first evaluate whether session was even needed in the first place.

Session variables are serialized and deserialized for every single page load whether the page uses that data or not. (EDIT: Craig pointed out that you have some level of control over this in .net 4 <a href="http://msdn.microsoft.com/en-us/library/system.web.sessionstate.sessionstatebehavior.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.web.sessionstate.sessionstatebehavior.aspx</a> However, this still has drawbacks, see comments to this answer.)

For single server instances this is okay as you are just pulling it from the local memory of your web server. The load on these apps tend to be pretty small so caching user specific information locally makes sense.

However, as soon as you move storage of session to another server you have increased the network requirements and page load times of your application. Namely, every page will result in the session data to be moved from the remote server, across the network wire, and into memory of the web server. 

At this point you have to ask yourself: is the load to pull this information from the database server directly as necessary more than pulling it from the session server every single time? 

There are few instances where pulling it from the database server as needed takes longer or results in more traffic than grabbing it from a remote session server.

Bearing in mind that a lot of people set up their database server(s) to also be session servers and you start to see why use of session doesn't make any sense.

The only time I would consider using session for load balanced web apps is if the time to acquire the data exceeded a "reasonable" amount of time. For example, if you have a really complex query to return a single value and this query would have to be run for lots of pages. But even then there are better ways that reduce the complexity of dealing with remote session data.

I have been tasked to scale out the session for an application. From my research the most obvious choice is to use the State Server session provider, because I don't need the users sessions to persist (SQL Server Session provider)

About the app:

<ul>
<li>Currently using InProc session provider</li>
<li>All objects stored in session are serializable</li>
<li>All objects are small (mostly simple objects (int, string) and a few simple class instances)</li>
</ul>

Before I dive head-first into the IT side of things and with the ability to provide a custom session provider with ASP.NET 4, should I even consider a custom session state provider. Why or why not? Are there any "good" ones out there?

Thanks!
 User feedback:

<ul>
<li>Why are we using session: persistence of data between postbacks (e.g. user selections)</li>
<li>How: user makes a selection, selection is stored. User leaves a page and returns, 
selections are restored. etc. etc.</li>
<li>Will be creating a web farm</li>
</ul>

Session State Server vs Custom Session State Provider

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我的任务是扩大一次申请的会期。根据我的研究，最明显的选择是使用状态服务器会话提供程序，因为我不需要用户会话来持久( Server会话提供程序)关于这个应用程序：当前使用InProc会话提供程序存储在会话中的所有对象都是可序列化的。所有对象都是小的(主要是简单对象(int、string)和一些简单的类实例)。在我深入到I...

问会话状态服务器与自定义会话状态提供程序
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会话状态服务器与自定义会话状态提供程序EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问会话状态服务器与自定义会话状态提供程序
EN