Performance Modules Optimization

Topics: Customizing Orchard
Jul 14, 2013 at 8:41 AM

A question about modules in orchard. I have read that it is a good practice to disable modules that you don't need in a production environment (makes sense :) ). So is it enough to only disable modules in the admin panel or do you need to remove (delete) the module from the file system?

Jul 14, 2013 at 9:29 AM
Disabling the features will prevent Orchard from registering types, so that in itself is a good step. However, Orchard still needs to load the assemblies and compile .csproj files, depending on configuration. So if you can delete unused modules, that would probably be even better to save on memory and warmup time. Note: I'm assuming all this, never really looked into it myself.
Jul 14, 2013 at 9:32 AM
Yeah, i am assuming the same. I think that a good approach would be the following:
  • Disable modules
  • If load times are still not acceptable then, delete modules.
What do you think?
Jul 14, 2013 at 9:38 AM
Makes sense to me.