For some reason I am seeing vbc.exe running in the task manager even though t have the site kept alive by calling the home page every 5 minutes. I am calling the home page myself when I see vbc.exe running which doesn't make sense to me  because the page should be already compiled and should be used by the runtime.

One of the reasons DNN could be slow is because some pages are being dynamically compiled during runtime.  So I was wondering maybe I should do a full site compilation before deployment where every aspx, asmx & cs file is compiled. I am not planning to change any code on the server, modify any file or add new modules and if I will, I will do a another recompilation and a redeployment.

Has anyone gone that route and knows it works with DNN and makes a difference in performance? My goal is to not have the asp.net runtime do any runtime compilation because it's a slow process.

Salame, please be aware, that precompilation requires some core changes, mainly the name of resource folders, which are constants and require some modules to be recompiled as well to work properly.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Personally I do NOT recommend pre-compiling, the benefit performance wise, in most cases is not worth taking yourself outside of the relm of being able to upgrade.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services