IIS application pool Configuration

Case:

A website has very few visits at ordinary times, and it feels very slow every time it accesses the website (the time is the same as the compilation time at the first runtime ).

Analysis:
The website is running in the working process. After the working process is idle for a certain period of time, it will be automatically recycled by IIS. The website will be re-compiled when the next user visits it. Therefore, websites with a large access volume do not have this problem, and websites with a small access volume may experience slow access speeds.

Solution:
Locate the application specified by the websiteProgramPool, "attribute" -- "performance" tab, remove the check boxes of "Idle timeout", "Disable working processes after idle for this period of time", "Request queue limit", and "core Request queue limit as (number of requests.