Do different forms of precompilation increase the impact?
I am using MVC3, ASP.NET4.5 and C #
There are a number of options when pre-compiling a web application:
- Don't combine.
- Don't merge, create a separate assembly for each page and do control.
- Consolidation of all outputs into one assembly.
- Combine the output of each individual folder into its own assembly.
- Merge all pages and control outputs into one assembly.
I am hosting on Azure sites.
Currently I have selected 3 which create a 2.5MB build.
I understand that at this point a PCode is generated ready for the Jitter to generate its own code at runtime, so the performance should be the same. However, I was wondering if there is a difference between these parameters. I currently chose option 3 because it seemed tidier.
Thank.
source to share
There should be a performance impact on the merge option you choose. How big? Undefined without testing, but intuitively, if there are more assemblies and files to access to access applications, it will take longer than accessing a single assembly. My guess is that the difference is tiny. The assemblies themselves should not affect performance, but your performance will suffer marginally in a non-merged scenario as there will be more files to process at runtime.
Additional resources that can help:
source to share