The strange question of ASP.net 2.0 X64

Asp.net| problem

64-bit CPU, 64-bit operating system, and finally to support the 64-bit ASP.net 2.0, and the disappointment is still not allow blog Park site running in 64.

Blog Park is currently running in 32-bit ASP.net 2.0, if the switch to 64-bit asp.net 2.0,web server CPU occupancy has been in 100%,asp.net 2.0 in the snail-like compiler application, remember May to upgrade the blog program to 64 bit asp.net After 2.0, the compilation was not completed for several hours.

Recently, the problem was discovered because IIS believed that the application pool exceeded virtual memory limits, frequently recycled application pools, and was recycled almost every minute, and the event log displayed such information as: A worker process with process ID of ' 2828 ' serving      Application pool ' app_cnblogs ' has requested a recycle because it reached its virtual memory. Even if you increase the application pool virtual memory settings, you cannot resolve the problem, view the virtual memory footprint of the process where the application pool is located, and do not reach the maximum virtual memory limit, possibly with the default settings for IIS recycling.