Frequent re-precompile on large site

[Jon Davis]

We maintain a large number of heavy traffic web sites hosted on limited
hardware resources. The traffic is such that pre-compilation is necessary
since each initial load of a page is at least two or three seconds per hit,
and multiplied across all sites the servers go down for a couple hours when
everyone hits it at once if there are subtle changes or additions.

Add to the frustrations, we are now integrating with a Perl-based CMS system
that outputs .aspx files that include references to our .ascx controls.

Compiling everything takes about one hour--compiling and deploying, with all
manual steps, is a three-hour process.

So obviously we are looking for a way to roll out incremental updates
without recompiling the whole site. Aspnet_compiler.exe has limitations, or
else I'm hoping it's just a matter of understanding. For example, is it
possible to precompile individual file revisions on a development
workstation and deploy the output to the live server without recompiling the
whole site? And, the -u parameter allows .aspx revisions but does it support
code-behind file revisions?

I have no doubt others deal with this problem all the time. I was wondering
if:

a) there is a detailed case study or tutorial for this problem available for
perusal, and

b) if anyone here has experience in this and might be available for very
short-term consulting such that we can reasonably trim down our three-hour
manual process to a much shorter automatic (or semi-automatic) process

Thanks,
Jon

 

[JP.Gantlin]

have you tried rebooting?

 

[Jon Davis]

have you tried rebooting?

I don't appreciate the remark. We have thousands of file assets;
recompilation and deployment taking 3 hours is entirely unavoidable, if we
cannot avoid recompiling the entire site.

Jon