缩小导航栏后封面图片(Shrink navbar AFTER cover image)

 一般的答案是“不要这样做”。 
 
 除此之外，您可以通过使用性能计数器获得很多收益。 如果内置计数器没有帮助，您可以创建自己的计数器。 
 
 除其他外，性能计数器可以让您了解如何通过负载测试重现性能问题。 
 
 下一个想法是缩小您感兴趣的区域。如果结果是您的Web服务访问速度很慢，那么对整个应用程序的性能没有任何影响。 
 
 接下来，确保已经为您的应用程序进行了检测，最好是使用配置。 企业库日志记录应用程序块非常适用于此，因为它允许您将日志记录添加到应用程序，但将其配置为关闭。 然后，您可以配置要记录的信息类型以及将其记录到何处。 
 
 这使您可以选择日志记录的成本，从记录到事件日志到记录到XML文件。 你可以在运行时决定这一切。 
 
 最后，您将无法使用dotTrace或其他需要重新启动IIS以及向正在运行的应用程序添加代码的内容。 不在生产中。 上述想法是为了不需要这样做。 

The general answer is "don't do it".
 
Other than that, you can gain a lot by using performance counters. If the built-in counters don't help, you can create your own.
 
Among other things, the performance counters may give you an idea of how to reproduce the performance problems through load testing.
 
The next idea is to narrow down the area you're interested in. There's no sense impacting performance for the entire application if it turns out to be your web service access that's slow.
 
Next, be sure to have instrumented your application, preferably by using configuration. The Enterprise Library Logging Application Block is great for that, as it allows you to add the logging to your application, but have it configured off. Then, you can configure what kind of information to log, and where to log it to.
 
This gives you choices about how expensive the logging should be, from logging to the event log to logging to an XML file. And you can decided this all at runtime.
 
Finally, you're not going to be able to use dotTrace or something else that requires restarting IIS an adding code to your running application. Not in production. The ideas above are for the purpose of not needing to do so.