高，波动在预编译的ASP.NET网站'％时间在JIT' [英] High, Fluctuating '% Time in JIT' on Precompiled ASP.NET Website

问题描述

对于具有预编译（可更新）的150 * .dll ASP.NET网站，' JIT中的％时间的一些可能原因通常是在应用程序预热（访问所有功能）并且没有
应用程序重新启动或可能生成新程序集的文件更改之后很长时间（> 60％）和波动？

我们期望为所有程序集生成的机器代码将在该应用程序域的持续时间内重复使用。缓存的机器代码的大小是否有限？在什么情况下，同一程序集需要在同一个应用程序域中重新启动？或者是否正在生成新的程序集？

：

• http://forums.asp.net/p/967386 /2959500.aspx

解决方案

它可以是组件发出的任何东西。 Linq表达式编译或正则表达式，没有被正确缓存。

With a 150 *.dll ASP.NET website that's precompiled (updatable), what are some possible causes for a '% Time in JIT' that is often quite high (> 60%) and fluctuating long after the application has warmed-up (all functionality accessed) and without app restarts or file changes that might generate new assemblies?

One would expect that the machine code generated for all assemblies would be re-used for the duration of that app-domain. Is there a finite size to the volume of machine-code that's cached? Under what scenarios would the same assembly need to be re-JIT'd in the same app domain? Or is it necessarily the case that new assemblies are being generated? Do factors such as memory pressure impact this performance counter?

Reference:

• http://forums.asp.net/p/967386/2959500.aspx

解决方案

It could be anything that does assembly emit. Linq Expressions compile, or regular expressions, that are not being cached correctly.

这篇关于高，波动在预编译的ASP.NET网站'％时间在JIT'的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！