如何使用缓存提高 ASP.NET MVC 3 网站性能？
我有一个类似 twitter 的网站，每 30 秒或更短时间更新一次。网站首页由三个部分组成：
左侧面板或右侧部分很少更新，但右侧部分有随机更改，因此我不需要缓存它们，但左侧或右侧的所有内容都需要缓存以提高性能。
当列出一些新内容时，中间的栏每隔几秒就会发生变化。所以我认为，如果我缓存它们，那么用户永远不会获得更新，那么
当数据库中发生更改时，我如何使用缓存并删除所有缓存。在 ASP.NET MVC 中做到这一点的任何技巧，
我所面临的整个问题是做一件常见的事情：-
如果我使用缓存，那么用户永远不会像网站一样得到更新，所以每当数据库中发生新事情时我都需要销毁缓存。那么我如何在 ASP.NET MVC 中做到这一点
I have a Website something like twitter who are update per 30 seconds or less. the website frontpage have three part:-
the leftside panel or right side part rarely to be updated but a section on rightside have random changes so i not need to cache them but everything in leftside or rightside i need to be in cache to improve performance.
the middle bar have changes in every few second when some new thing come to listed. so i thing that if i cache them then the user never get update so
how i can use cache and remove all cache when changes happend in database. any trick to do that in ASP.NET MVC
the whole question i have for doing a common thing that :-
if i use cache then user never got update soon as website have so i need to destroy cache whenever new thing goes happened in databse. so how i can do this in asp.net mvc
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您需要使用
OutputCacheAttribute或类似的东西。该操作过滤器“代表一个属性，用于标记其输出将被缓存的操作方法”。当操作更新数据库时，应缓存生成的视图，因为它会覆盖以前缓存的数据。You need to use the
OutputCacheAttributeor something similar. This action filter "represents an attribute that is used to mark an action method whose output will be cached." When an action updates the database, the resulting view should be cached, because it is overwriting the previously cached data.您正在寻找的是 SqlCacheDependency。请参阅此处。
What you are looking for is SqlCacheDependency. See here.
您应该能够使用部分视图并标记要缓存的...在谷歌中搜索缓存部分视图...
您可以查看缓存依赖项以刷新缓存...或者您可以让缓存在给定的时间内过期时间段，它最终会赶上实时数据...
在不完全理解问题的情况下很难选择最佳解决方案，但这应该为您指明正确的方向...
You should be able to use partial views and mark the to be cached... Search google for caching partial views...
You could look at cache dependencies to flush the cache... or you could just have your cache expire in a given time period and it would eventually catch up to the live data...
it is hard to pick the best solution without understanding the problem fully but that should point you in the correct direction...