We recently switched some of our sites from deflate to gzip and noticed a significant increase in cpu load on our servers.
相关问题
- How to make a .svc file write to asp.net Trace.axd
- How to deploy python flask application in conda ba
- ASP.NET won't compile to debug
- Web server farms with IIS ? Basic Infos [closed]
- how do i manually configure a virtual directory in
相关文章
- 请教IIS URL重定向的问题
- 一个愚昧的问题,在一台电脑/云服务器下,假设某个系统访问量大,给他在IIS部署多个同样的网站和部署一
- .Net5 程序发布到IIS10
- 程序是如何接收并启动监听 IIS 站点设置的端口号的?
- IIS App Pools & Static Classes
- ASP.NET code to detect whether IIS “Windows Authen
- Installing Web Deploy on IIS 7+ with Shared Config
- ASP.NET is not authorized to access the requested
gzip is, basically, deflate with some additional headers. So there should not be a significant performance hit. Now, maybe your deflate tool is just more efficient than your gzip tool. Are you using the same tool for both compressions or two different ones?
Is it possible that you are experiencing cache miss? That is, compressed content is sometimes cached compressed but switching compression schemes would (or at least should) invalidate that cache causing dramatically increased cpu utilization. Did you try switching it back?