64-bit CPU, 64-bit operating system, and finally ASP.NET 2.0 that supports 64-bit. What is disappointing is that the Blog Park website still cannot run in 64-bit.
The Blog Park website is currently running on 32-bit ASP.NET 2.0. If it is switched to 64-bit ASP.NET 2.0, the Web server CPU usage is always at 100%, and ASP.NET 2.0 is compiling the application at a snail's pace. Remember to upload the Blog program in May After upgrading to 64-bit ASP.NET 2.0, the compilation took several hours but was not completed.
Recently, the cause of the problem was discovered. It turned out that IIS believed that the application pool exceeded the virtual memory limit and frequently recycled the application pool, almost every minute. The event log showed this information: A worker process with process id of '2828 ' serving application pool 'APP_CNBlogs' has requested a recycle because it reached its virtual memory limit. Even increasing the application pool virtual memory settings does not solve the problem. Check the virtual memory usage of the process where the application pool is located, and it does not reach the maximum virtual memory limit. Memory limit, maybe IIS is recycling according to the default settings.