blocks|key|1654665|text|Cache在Application作用域中，其目的是减少获取数据的次数。会话位于用户的会话作用域中，目的是提供特定的用户状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654666|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Cache is in the Application scope with the purpose of reducing the number of times a piece of data is obtained. Session is in a user's session scope with the purpose of giving a particular user state.

blocks|key|1439975|text|这取决于你如何为ASP.NET配置会话。你是在数据库中存储会话还是在内存中存储会话？如果在内存中，您使用的是单独的服务器，还是使用当前的for服务器进行会话？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1439976|根据如何为您设置内容，当您使用datatable之类的东西时，可能会影响性能，这告诉我您可能正在存储大量数据。|1439977|此外，如果用户不接受cookie并且您已将ASP.NET设置为无cookie模式，则每个用户都会存储会话，并通过存储在会话cookie中或网址上的会话票证来检索会话。您缓存的任何内容都将在应用程序级别缓存，并可供所有用户会话使用，这些用户会话可能是您想要的，也可能不是。|1439978|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Well it depends on how you have session configured for ASP.NET. Are you storing session in a database or in memory? If in memory are you using a separate server or are you using the current webserver for session?

Depending on how things are set up for you there may be performance implications when you are using something like a datatable which tells me that you are perhaps storing large amounts of data.

Also Session is stored per user and is retrieved per user by means of their Session ticket that is stored either in a Session cookie or on the URL if they do not accept cookies and you have set up ASP.NET to cookieless mode. Anything that you cache will be cached at the application level and will be available to all user sessions which may or may not be what you want.

blocks|key|1654735|text|会话是针对每个用户的，缓存是针对应用程序的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654736|缓存中的项可以并且将根据IIS辅助进程的过期时间(滑动或固定)和内存约束自动删除。|1654737|因此，从根本上说，Cache中的项永远不会保证存在，但会话将一直存在，直到会话结束。|1654738|在每个用户的基础上存储项目(通过Session或创造性地使用Cache)可能会导致大量的内存使用，应该仔细考虑。|1654739|最重要的是，如果IIS重置了工作进程，您可能会丢失缓存和会话。|1654740|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Session is per user, Cache is for the application.

Items in Cache can and will be removed automatically based upon expiration times (sliding or fixed) and memory constraints of the IIS worker process. 

So basically items in Cache are never guaranteed to exist but Session will stay there until the session ends.

Storing items on a per-user basis (via Session or a creative use of Cache) can lead to a lot of memory usage and should be considered carefully.

On top of all of this, if IIS resets the worker process, you can lose your Cache and Session.

blocks|key|1654765|text|一个重要的区别是，缓存中的项可以在指定的时间后过期(将从缓存中删除)。放入会话中的项将一直保留在那里，直到会话结束。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1654766|当可用内存量变小时，ASP.NET还可以从缓存中删除项目。|1654767|另一个区别是:会话状态可以保持在外部(状态服务器、SQL服务器)，并在web应用程序的多个实例之间共享(用于负载平衡)。缓存的情况并非如此。|1654768|除了这些区别(正如其他人所指出的)：会话是按用户/会话的，而缓存是按应用程序的。|1654769|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

One important difference is, that items in the cache can expire (will be removed from cache) after a specified amount of time. Items put into a session will stay there, until the session ends.

ASP.NET can also remove items from cache when the amount of available memory gets small.

Another difference: the session state can be kept external (state server, SQL server) and shared between several instances of your web app (for load balancing). This is not the case with the cache.

Besides of these differences (as others have noted): session is per user/session while cache is per application.

blocks|key|1654820|text|参见this+answer。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1654821|会话可能会降低应用程序的性能，除非您使用诸如memcached或velocity之类的后端提供程序。一般来说，你应该避免使用它。|1654822|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/167873/repeated-cookie-query-or-storing-in-viewstate-which-is-the-better-practice#168050^0|2|B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

See <a href="https://stackoverflow.com/questions/167873/repeated-cookie-query-or-storing-in-viewstate-which-is-the-better-practice#168050">this answer</a>. 

Session can kill your app performance, unless you use some backend provider like memcached or velocity. Generally you should avoid it.

blocks|key|1440215|text|据我所知，这完全取决于你的需要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1440216|当你需要维护用户的状态时，你在使用会话时必须非常小心。默认设置是“InProc”，它使用单个服务器的内存，在基于云的应用程序中不能很好地工作。这可能适用于那些在多实例web场环境中托管应用程序的人。Windows+Azure负载平衡器在连接的节点内使用循环分配。|1440217|您在会话存储中有多个选项。SQL+Server还可以用作会话状态的存储。自定义会话技术在azure上可用，如表、存储、提供程序等。|1440218|缓存也存储在服务器的内存中，但它与用户无关。同一池中的任何用户都可以访问应用程序缓存数据。简而言之，在云上，我们需要使用云提供商提供的缓存服务。Azure提供Windows+Azure分布式缓存服务。|1440219|事实上，在应用程序中应用状态管理技术时，开发人员并不关心该技术的影响。它|1440220|如果您的客户端没有云支持，则不必担心云方案|1440221|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

As far as I know, it all depends on your needs. 

Whenever you need to maintain state for the users, then you have to be very careful while using sessions. The default setting is 'InProc', which uses the individual server's memory, does not work well in Cloud-based applications. This may be applicable for those of you who host your application in multi-instance web-farm environments. Windows Azure load balancer uses round-robin allocation within connected nodes. 

You have multiple options in the session storage. SQL Server can also be used as a storage of session state. Custom session techniques are available on azure like table storage provider etc.

The Cache is also stored on the server's memory, but it doesn't have a concern with the users. Any user within the same pool can access the application cache data. In short, on the cloud, we need to use Caching service provided by the cloud providers. Azure provides Windows Azure distributed caching service. 

As a matter of fact, developers do not care about the impact of state management techniques when applying the technique in the applications. It

"If your client doesn't have cloud support, then you don't worry about the cloud scenarios"

What is the difference between storing a datatable in Session vs Cache? What are the advantages and disadvantages?

So, if it is a simple search page which returns result in a datatable and binds it to a gridview. If user 'a' searches and user 'b' searches, is it better to store it in Session since each user would most likely have different results or can I still store each of their searches in Cache or does that not make sense since there is only one cache. I guess basically what I am trying to say is that would the Cache be overwritten.

Advantages of Cache vs Session

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

在Session中存储datatable与在Cache中存储datatable有什么区别？优点和缺点是什么？因此，如果它是一个简单的搜索页面，它在datatable中返回结果并将其绑定到网格视图。如果用户'a‘搜索和用户'b’搜索，最好将其存储在会话中，因为每个用户最有可能有不同的结果，或者我仍然可以将他们的每个搜索存...

问缓存与会话的优势
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缓存与会话的优势EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缓存与会话的优势
EN