Must Have

• Set debug=”false” in web.config
• Use a precompiled build.
• …from a developer command prompt with build precompiled
• …from Visual Studio’s Publish dialog.
• Use release configuration
• Disable unused modules.

Should Have

• Delete unused modules (be careful with dependencies) before compilation.
• Enable these Features
• Performance > Combinator (Configure in Settings > Combinator)
• Performance > Orchard.Caching (no configuration)
• Performance > Output Cache (Configure in Settings > Cache)
• Performance > SysCache (no configuration)
• Hosting > Warmup (Configure in Settings > Performance)

Nice to Have

• Use SQL Server not SQLCe
• Enable these Features
• MS Azure Database Cache
• MS Azure Output Cache
• Keep Alive (if idle timeout is an issue)

Appendix : Some of our standard settings

If it isn’t noted here, we use default settings for each feature (e.g. We use Combinator defaults)

Output Cache Settings

We set the cache to last one year (in seconds). Everything else is default.

Warmup Settings

We generate warm-up pages every 90-minutes.

Visual Studio Publish Settings

Package/Publish Web (Orchard.Web > right click > Properties)

Publish Web > Settings (Orchard.Web > right click > Publish > Settings)

Advanced Precompile Options

Resources

http://orcharddojo.net/orchard-resources/Library/DevelopmentGuidelines/OrchardPerformanceOptimization

http://azure.microsoft.com/blog/2014/01/21/orchard-cms-with-azure-cache-on-windows-azure-websites-waws/

http://msdn.microsoft.com/en-us/library/aa983464%28v=vs.110%29.aspx

http://msdn.microsoft.com/en-us/library/dd410108%28v=vs.110%29.aspx

http://msdn.microsoft.com/en-us/library/hh475319%28v=vs.110%29.aspx

http://technet.microsoft.com/en-us/library/cc731903%28v=ws.10%29.aspx

http://stackoverflow.com/questions/14041875/slow-orchard-performance-on-windows-azure