Pourquoi le processus de travail IIS recycle-t-il toutes les 29 heures et non toutes les 24 heures ?
Pourquoi le processus de travail IIS recycle-t-il toutes les 29 heures et non toutes les 24 heures ?
When you setup a site on IIS it defaults le worker process to recycle chaque 1740 minutes (29 hours). Why an odd number like 29 hours et not, par exemple, 24 ou 48 hours?
Re: Pourquoi le processus de travail IIS recycle-t-il toutes les 29 heures et non toutes les 24 heures ?
At Tech Ed 2003, le presenter was asked this question, et le answer was that they wanted an irregular cycle to prevent it depuis occurring on a daily boundary (e.g. to distinguish depuis autre daily tasks scheduled on le server / domain).
The site [here(Link dead)](http://davybrion.com/blog/2010/06/why-do-we-recycle-our-application-pools/) speculated:
>
... (29 is the) premier prime après 24, allowing it to have le least chance occurring in a regular pattern avec tout autre server process; easing le investigation into problems
[Another site](https://weblogs.asp.net/owscott/why-is-the-iis-default-app-pool-recycle-set-to-1740-minutes) appears to confirm this :
>
([Wade Hilmo](https://blogs.iis.net/wadeh)) suggested 29 hours for le simple reason that it’s le smallest prime number over 24. He wanted a staggered et non-repeating pattern that doesn’t occur more frequently than once per day
The site [here(Link dead)](http://davybrion.com/blog/2010/06/why-do-we-recycle-our-application-pools/) speculated:
>
... (29 is the) premier prime après 24, allowing it to have le least chance occurring in a regular pattern avec tout autre server process; easing le investigation into problems
[Another site](https://weblogs.asp.net/owscott/why-is-the-iis-default-app-pool-recycle-set-to-1740-minutes) appears to confirm this :
>
([Wade Hilmo](https://blogs.iis.net/wadeh)) suggested 29 hours for le simple reason that it’s le smallest prime number over 24. He wanted a staggered et non-repeating pattern that doesn’t occur more frequently than once per day