.net - When my large ASP.NET site is updated, IIS has to recompile a lot of it. Is there a way to cut down my compile time significantly? -
dotnetnuke large asp.net cms pre-compiled, of modules contained within.
when deploy our dotnetnuke site changes, have 2 bits of recompilation occur upon first page hit.
- application-level recompilation occurs when dll replaced in bin folder
- each time individual module accessed first time, recompiling occurs on specific module.
is there way allocate more of cpu capacity compiling asp.net sites in iis 7?
- i'd use more 1 core, or @ least reduce recompile time.
q&a
you should use pre-compiled asp.net. why aren't you?
- we using pre-compiled asp.net. because asp.net app compiled dll not mean asp.net runtime not additional recompiling in order serve vistiors.
how know it's recompiling , not populating cache or something?
- viewing task manager on server shows 50% cpu usage compiler executable during aforementioned page hits. why 50%? 2-core server.
set <compilation optimizecompilations="true" />
specifies whether dynamic compilation recompile entire site if top-level file changed. top-level files include global.asax file , files in bin , app_code folders. if true, changed files recompiled.
source: compilation element (asp.net settings schema)
more information pros , cons can found @ understanding asp.net dynamic compilation, under optimizing dynamic compilation. primary cause of errors removal or changes in existing method signatures, causing compiled pages throw missingmethodexception until recompiled.
you reducing batch size batch compilation, or disable completely. believe reduce compilation times single pages, generate more assemblies , consume more memory.
Comments
Post a Comment