If so, it is largely caused by the precompiling (also translated as preheating) mechanism of. Net. There is no way to solve this problem. We can only precompile as early as possible through some settings, not when requested. But this method can only say that if the precompilation is over when the request is made, it will be soon; If precompilation is not completed, it will still be slow. Specific practices can be Baidu "IIS ASP.NET preheating" keywords.

But in general, the precompiling process will be completed in a few seconds. If it is much longer than this time, then there are other factors that affect the problem. Generally speaking, we can start from two aspects:

1, digital signature verification timeout: it can be solved by disabling digital signature verification, or through Baidu "ASP". NET Authenticode signature ";

2. There is a performance bottleneck code (ASP) in the 2.Application_Start event. The core of. NET corresponds to startup), so you need to do Profiling to check it out slowly.