ASP.net会话状态信息服务 [英] ASP.net session state service information

查看:162
本文介绍了ASP.net会话状态信息服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在那里你可以得到ASP.NET状态服务如信息它的工作原理,性能,行为特征等。
看过互联网上,但在深度信息或专用于主题的文章找不到。
谢谢

Where can you get information on the ASP.NET State Service e.g. how it works, performance, behaviour characteristics etc. Have looked on internet but cant find in depth information or an article dedicated to the subject. Thanks

推荐答案

  • ASP.NET Session State: Architectural and Performance Considerations (Blog Post)
  • ASP.NET Session State (MSDN)
  • Improving .NET Application Performance and Scalability (MSDN)
  • Session State (MSDN)
  • 这可能会或可能不会使用你的..

    Which may or may not be of use to you..

    总之,它的工作原理是这样的:

    In short, it works like this:

    InProc会话状态是最快的,但它也是在过程中,这意味着它不共享(读的没有良好的网络农场的),并丢失,如果该进程崩溃。

    InProc Session State is the fastest, however it is also in-process, meaning it is not shared (read "no good for web farms"), and is lost if the process crashes.

    状态服务(aspnet_state.exe的)仍是pretty该死的快,但有一些开销,由于工作进程和服务本身之间的编组。可能是一件好事,因为IP地址可以在配置获得通过,这意味着它能够在自己的机器上运行即可。它是从工作进程还出的进程,这意味着它可以生存进程崩溃。因为它可以在一台机器上运行,可以共享提供状态的所有客户端使用同一台机器。

    State Service (aspnet_state.exe) is still pretty damn quick, but there is some overhead due to the marshalling between the worker process and the service itself. Can be good because IP addresses can be passed in the config, meaning it can run on its own machine. It is also out-of-process from the worker process, meaning it can survive a process crash. Since it can run on a single machine, state can be shared provided all clients use the same machine.

    SQL服务器(或其他自定义提供) - 阻碍(并不总是)是最慢的他们全部,特别是由于什么可能是更大量的磁盘I / O。然而,这也是更强大的解决方案之一,因为状态可以保存在磁盘上,不仅意味着它可以在Web服务器上生存进程崩溃,但它可以存活服务器崩溃本身(一旦数据库恢复联机,状态恢复)。再加上这个集群可以提供坚如磐石的会议系统。

    Sql Server (or another custom provider) - Tends (not always) to be the slowest of them all, especially due to what could potentially be a lot more disk I/O. However, this is also one of the more robust solutions since the state can be persisted to disk, meaning not only can it survive a process crash on the web server, but it can survive a server crash itself (once the DB is back online, the state is restored). Coupled with clustering this can provide a rock-solid session system.

    这篇关于ASP.net会话状态信息服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆