The 64-bit CPU and 64-bit operating system finally waited for the 64-bit ASP. NET 2.0 to support, and the disappointing thing was that the blog site still could not run on 64-bit.
The blog site currently runs on 32-bit ASP. NET 2.0. If you switch to 64-bit ASP. NET 2.0, the CPU usage of the Web server remains at 100%, and ASP. NET 2.0 compiles applications in a snail like manner. ProgramI remember that after I upgraded my blog program to 64-bit ASP. NET 2.0 in February, it was not completed after several hours of compilation.
Recently, I found the cause of the problem. It turns out that IIS considers the application pool to exceed the virtual memory limit and frequently recycles the application pool, which is recycled almost every minute. The Event Log displays the following information:
A worker process with process ID of '000000' serving application pool 'app _ cnblogs' has requested a recycle because it reached its virtual memory limit.
Even if the virtual memory settings of the application pool are added, the problem cannot be solved. Check the virtual memory usage of the process where the application pool is located and the maximum virtual memory limit is not reached, IIS may be recycled according to the default settings.
