我们是否可以加快或避免使用imageresizer对图像请求进行授权?

I've just set-up newrelic on an azure cloud service and now sifting through the logs to make any improvements.

我刚刚在azure云服务上安装了newrelic，现在我正在对日志进行筛选，以便进行任何改进。

For the imageresizer requests, I'm noticing a significant amount of time in AuthorizeRequest, here's a typical transaction:

对于imageresizer请求，我注意到AuthorizeRequest有大量时间，这里有一个典型的事务:

1. DotNet AuthorizeRequest 57.6 (%)
2. DotNet以57.6(%)
3. External Stream[x.blob.core.windows.net] 24.6
4. 24.6外部流[x.blob.core.windows.net]
5. DotNet AcquireRequestState 14.0
6. DotNet AcquireRequestState 14.0
7. DotNet MapRequestHandler 2.7
8. DotNet MapRequestHandler 2.7
9. DotNet ResolveRequestCache 0.5
10. DotNet ResolveRequestCache 0.5
11. DotNet Integrated Pipeline 0.3
12. DotNet集成管道0.3
13. DotNet UpdateRequestCache 0.2
14. DotNet UpdateRequestCache 0.2
15. DotNet SendResponse 0.1
16. DotNet SendResponse 0.1

Is AuthorizeRequest actually where the grunt of the image processing occurs? Hence the high percent of batch? Or can I reduce the time spent here re-configuring the app as there needn't be any authorization required for the images?

授权实际上是图像处理出现的咕哝处吗?因此批次的百分比很高?或者我是否可以减少在这里重新配置应用程序的时间，因为图像不需要任何授权?

1 个解决方案

#1

Yes, everything happens during AuthorizeRequest, as this permits the request to be rewritten to a static file (if cached) prior to ProcessRequest.

是的，一切都发生在AuthorizeRequest过程中，因为这允许在ProcessRequest之前将请求重写为静态文件(如果缓存)。