Orchard is loading too slow after each recompilation giving ASP.NET 404

Topics: Administration, Core, General, Troubleshooting, Writing modules
Jan 12, 2013 at 2:00 AM
Edited Jan 12, 2013 at 1:50 PM

We have about 30 modules and 15 themes in our set up. Recently we moved to Orchard 1.6. Since then every time we recompile a module we have to restart the iis process because it caches the assemblies and we cant see the changes until we restart it. It is not a big deal to kill the IIS. The big deal is to wait while Orchar initializes itself after each rebuild and restart of the IIS. It takes on average about 2 minutes to get it up. Better yet we get 404 errors on attempts to get a page just after the restart. As you can see it is pain in the ass because it slows down the team and the productivity is low.


How can we set up version 1.6 in a way so that it doesn't cache the assemblies and doesn't require a IIS restart on every rebuild (just like it worked before in a previous version)?

Jan 12, 2013 at 7:37 AM

Neither are normal. Changes on a module should be picked up automatically. You shouldn't even need to recompile. 2 minutes to restart is also highly abnormal. You might want to profile that.

Jan 12, 2013 at 12:20 PM
Edited Jan 12, 2013 at 12:20 PM

Any ideas on what needs to be done to troubleshoot it?

Jan 12, 2013 at 12:26 PM

Perhaps there's anything suspicious in the logs (under App_Data/Logs)?

Jan 12, 2013 at 1:47 PM

Nothing suspicious there, namlely nothing at all. I already checked.

Jan 14, 2013 at 11:55 PM

As I said above, you should profile it.