加入收藏 | 设为首页 | 会员中心 | 我要投稿 李大同 (https://www.lidatong.com.cn/)- 科技、建站、经验、云计算、5G、大数据,站长网!
当前位置: 首页 > 编程开发 > asp.Net > 正文

asp.net – 是否值得在IIS7中启用动态压缩?

发布时间:2020-12-15 22:53:58 所属栏目:asp.Net 来源:网络整理
导读:我正在尝试寻找所有可能的方法来提高我的网站性能.我正在考虑在服务器级别启用动态压缩,但关注性能命中(压缩页面的缓存 – 文件损坏 – 服务器上的开销). 我应该放弃使用IIS 7的动态压缩吗?那里的模块比内置的压缩??模块做得更好吗? 解决方法 绝对.请参阅
我正在尝试寻找所有可能的方法来提高我的网站性能.我正在考虑在服务器级别启用动态压缩,但关注性能命中(压缩页面的缓存 – 文件损坏 – 服务器上的开销).
我应该放弃使用IIS 7的动态压缩吗?那里的模块比内置的压缩??模块做得更好吗?

解决方法

绝对.请参阅这个 article在IIS 7中前10名的性能改进.

引用文章:

Bandwidth Reduction from Compression

It comes as no surprise that bandwidth costs are one of the top costs of running an Internet-facing datacenter. In addition,the bandwidth required to deliver requested content is a key factor in the perceived responsiveness of your application.

One of the most effective ways to reduce the bandwidth needed to deliver the application responses is to use HTTP compression. This can reduce the size of the response by a substantial amount,often by a factor of 10 when applied to easily compressible text content such as HTML. The best part is that virtually all desktop browsers support it,and decompression costs on desktop hardware are minor compared to the latency savings from sending less data. And since compression is based on Content-Encoding negotiation defined in the HTTP 1.1 protocol,enabling it is safe for clients that do not support compression—these clients simply receive an uncompressed version of the content.

(编辑:李大同)

【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!

    推荐文章
      热点阅读