How does compiled XSLT work in IIS?

Question

My XSLT was compiled via xsltc, performance is greatly improved. However, I wonder how compiled XSLT works in IIS? Will there be caching of the compiled XSLT instance in IIS after the 1st JIT'ing. Since I see that my page is a bit slow in response from the server, but if the page after calling it once, subsequent access to the page will be faster. Therefore, I suspect that all conversion processes have not been cached for a long time on the server side.

Answer 1

I believe that your experience of slow response to loading the first page may mainly depend on the "pool reuse" effect that is used in IIS. All loaded assemblies for your application are cleared from memory if you do not send a request to IIS (the default time is 20 minutes). Then, when you execute your first request on the server after this pause, your application starts up and takes quite a while. For IIS 7.5, a “Heating Module” has been developed. You can touch it here: http://www.iis.net/download/applicationwarmup. If you experience this effect when loading not only the first page to the entire site after a period of inactivity, but also for each new page of the site. So the likely explanation for this effect is that for other pages, your browser just uses the cache. (IE, for example, crazy in caching)