In Tip 7, I talked about output caching.
在技巧7中，我讨论了输出缓存。
Any text that represents custom output caching requirements.
表示自定义输出缓存要求的任意文本。
Output caching setup via a script so we do not have to manually set it up after each deploy.
输出缓存设置通过一个脚本，所以我们不需要手动设置在每个部署。
This means that when you use kernel-mode caching with IIS and ASP.NET output caching, you'll see unbelievable performance results.
这就表示，当您将内核模式缓存与IIS和ASP.NET输出缓存一起使用时，就会看到令人不敢相信的性能结果。
If you use session state in a page that has output caching enabled, and if the application runs on IIS 6.0, then you need to turn off kernel-mode output caching.
如果您在启用输出缓存的页中使用会话状态，并且应用程序在IIS 6.0上运行，则您需要关闭内核模式输出缓存。
You'll still get the benefit of output caching, but because kernel-mode output caching is substantially faster than ordinary output caching, the caching won't be as effective.
您仍将受益于输出缓存，但是因为内核模式输出缓存比普通输出缓存快得多，所以缓存不会同样有效。
During editing, without caching, the update feed is executed whenever its output is previewed.
编辑过程中，如果没有缓存，则只要输出被预览，更新数据源就会执行。
Advanced caching (which provides options to selectively cache content by session, users, and so on), provides the same output as the basic caching option.
高级高速缓存(提供按照会话、用户等选择缓存内容的选项)，提供了与基本高速缓存相同的数据选项。
However if you have caching enabled, the output will be cached with the rest of the template.
但当开启缓存时，该输出会将与余下的模板一起缓存。
NET caching allows you to use a number of techniques to store page output or application data across HTTP requests and reuse it.
NET缓存允许您使用多种技术跨http请求存储页输出或应用程序数据并对其进行重复使用。
However if you have caching enabled, the output will be cached with the rest of the template.
但当打开缓冲设置时，该输出会被其它模板缓冲。
Caching Multiple Versions of User Control Output.
缓存用户控件输出的多个版本。
Caching Multiple Versions of User Control Output.
缓存用户控件输出的多个版本。
应用推荐