高波动“的JIT％时间”在precompiled ASP.NET网站 [英] High, Fluctuating '% Time in JIT' on Precompiled ASP.NET Website

问题描述

通过一个150 * .DLL ASP.NET网站的 precompiled （更新），什么是对一些可能的原因'％在JIT 时间'那往往是相当高（> 60％）和波动应用程序已久后暖机（全功能接入）和无
重新启动应用程序或文件的更改可能会产生新的组件？

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?

人们预计，为的所有的将被重新用于该应用程序域的时间组件所产生的机code。是否有一个有限的尺寸到的缓存机器code的量？在什么情况下会在同一组件需要重新JIT'd在同一个应用程序域？抑或是必然正在生成的新组件的情况下？难道因素，如内存pressure影响此性能计数器？

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?

参考

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

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

推荐答案

这可以是任何东西，它装配发射。 LINQ的防爆pressions编译或常规前pressions，即未正确缓存。

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

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