As an AspDotNetStorefront Enterprise Partner, Guidance has built dozens of sites on the ML platform, including Z Gallerie, Simplicity, Caltech, Bentley Prince Street, Drum Channel, A.C. Moore, GEARYS, Pollstar, and many others. Each site has had its unique set of requirements, but after building so many of them, we began identifying standard ways to enhance the performance of AspDotNetStorefront. We like sharing our findings so we thought we would post some of them. Here they are:
- Data caching should be turned on for the website. Any customizations that involve database calls should leverage the data caching in AspDotNetStorefront and turn on/off with the caching switch in the admin website/backend.
- Remove unnecessary database calls from the website (including those for features that are turned off), especially from the header since it is loaded in every page.
- Ensure that no other services (i.e. antivirus software with firewalls, etc.) are running on the server, as they might slow down the performance of the website.
- Configure SQL Server temporary tables to use a temporary file per core, so that cores aren’t locking each other out on one file.
- Search stored procedure is very big and generally, very intensive. Improvements to this could boost performance. Common searches could also be cached.
- Configure static and dynamic compression within IIS to find the appropriate balance between smaller file sizes served and compression performance.
- Use a Content Delivery Network (CDN). Determine an appropriate traffic threshold at which it is cost-effective to leverage a CDN. In doing so, one can plan for the CDN at the beginning of a project, rather than implementing it as an emergency solution to a poorly performing site.
If this list is helpful, let us know!
---
Radu M.
Guidance
