IIS application initialization module and memory management -

i researching iis application initialization module , can see, when using alwaysrunning option start mode setting application pool, starts new worker process run if there isn't requests. when applying option starts process automatically.

my concern memory management , cpu usage, how handled since process runs.

how can compare setting start mode ondemand , increase idle time minutes couple of days? way, guess, process run in idle mode x days before it's terminated, , reinitialized on next request , keep running couple of days. if set minutes let's 1.5 days, bound use application @ least once day, persist process runtime , never terminated.

can share experience regarding topic?

thanks

i have multisite application runs few sites under separate app pools. set ondemand start mode , idletime 1740 minutes, use page output cache app different times different page types. there nhibernate behind scene , db mysql.

the active site have more 100k visits per day , never idle. when starts if recycle, need 30 seconds 2 minutes became full operable depending on requests @ moment , cpu usage going 40% 70%. after site cpu usage low (0-4%) if there no new entries in db , memory usage around 3gb when cached. cpu going 20% if @ moment new request (for not cached content) , there new entry saving. page output cache works on first come first served base maybe can cause little problem while caching done - user must wait, little more cpu caching.

the biggest problem in case using nhibernate , mysql page output cache resolved problem me when decided cache page modules , content. realize better application starve memory cpu. 3.5k visitors @ 1 moment when cached gave me same memory usage (3gb) , cpu (server overall) around 40% other sites using around 1-1.5gb memory , cpu never more 20% @ start. application same settings app pool , using mssql ef can't notice run on server. used 10-60 users in minute there not content except embedding codes , use 1-5% cpu , never more 8mb memory. on recycle less 10 seconds.

with experience can tell depends on application serves , how works :) , how content have.

if use ondemand long idletime same alwaysstart , process not used @ moment. if use ondemand short idletime more need cpu start process.