Learning asp.net is some time, there is no special concern for the speed of each time the first runtime. Then I saw such a paragraph when reading the book:
The first time you access the ASP.NET page ... the most remarkable thing you will see differentiating it from the traditional ASP version is the amount of time it takes for the page to load. It is slower. Quite a bit slower, in fact. Any subsequent access to that page, however, will be markedly faster. The overhead you will see on the first access is the launching of the ASP.NET worker process plus the parsing and compilation of the .aspx files into an assembly.
The ASP.NET WORKER Process that this passage said is ASPNET_WP.EXE. This process can be seen in the task manager. Just don't understand that a significant difference between ASP.NET and traditional ASP is that the page of ASP.NET is to compile first. This is why I can always see a .dll file in the bin directory of the project. So where is the overhead of the first call? Load the expenditure of ASPNET_WP? During this pass, my doubts:
.
This reminds me of another server-side scripting language JSP. .jsp also compiled into an Applet class when called for the first time. Therefore, it will also feel the delay in the speed of the speed as the first call as mentioned above. The next call will be flying. However, there will be a temporary directory in Tomcat to store compilation .CLASS, this compile page file in IIS is stored? In addition, in this way, then why ASP.NET must be compiled before it? do not understand.
