How to improve performance

Performance is dependent on several factors such as hardware, network speed, server load, etc. There are several things you can do on the software side to improve performance:

• Ensure you are running .NET 4.5+ framework.
• Ensure you are running the latest version of Revindex Storefront running the newest display templates. Newer releases often have significant performance enhancements.
• Enable IIS or DotNetNuke compression.This will significantly improve download time.
• Install Revindex Optimizer to speed up page loading time by up to 50%.
• Remove any unnecessary module controls on your page (side banner, footer, etc.).
• Set your DotNetNuke Cache Settings to "Heavy" under Host > Host Settings page. Please note caching takes effect and builds up speed after the first page visit.
• Make use of content delivery network (CDN) to host your common client scripts under Host > Host Settings page.
• Make use of Client Resource Management composition and minify files under Host > Host Settings page.
• Make sure to Enable Event Log Buffer under Host > Host Settings page to avoid writing to disk everytime a log is generated.
• Uncheck the Auto-Sync File System under Host > Host Settings page if you don't use FTP to avoid querying the disk for new files.
• Reduce the high frequency runs of unimportant jobs under Host > Schedule page. For example, you don't always need to index your search every minute and can increase to 15 minutes.
• Uninstall extensions that you don't use under Host > Extensions page to reduce memory consumption.
• Ensure your hosting does not place a limit your application pool's memory or CPU usage.
• If you have a low traffic site, ensure your site is up and running using a keep-alive service to ping your site every 15 minutes. If your site idles too long, your hosting provider or IIS may shut down the process causing the first visit to take a long time to start up again.

In terms of hardware changes:

• Ensure you have lots of free memory on the server so that your OS is not swapping to disk and the Web server is able to cache as much data as possible.
  
  Ideally, ensure the system can cache all your products to memory. You can roughly calculate how much memory is needed for simple products = Avg. DB row size X Number of products X 10 factor. The factor of 10 will increase quickly if your product is complex and have many variants and attributes, so please test accordingly. For example, if your database product table uses about 1 KB of storage per row and you have 10,000 products, you can approximate a memory consumption of 100 MB just for caching products. To find the row size, you can simply view your table properties and look for the table storage size and divide by the number of rows in that table.
• Get faster hard drives for your database and file server. It's about the number of IO per second and not about storage size (SSD or 10K/15K rpm hard drives in RAID are recommended).
• Get a very fast CPU for your Web server especially if you intend to use a lot of dynamic rules and promotions.
• Revindex Storefront supports Web farm configuration allowing you to spread the load over multiple Web servers.
• Ensure you have a fast ethernet connection between your Web server and database server if they're on separate machines (1 Gbps or higher is recommended).
• Ensure you have a fast public network (100 Mbps or more).

How you configure your Storefront will also determine the general performance of your shop:

• Group your products using multiple categories and sub-categories to avoid displaying too many products on a single page. It's generally ineffective to list thousands of products on one category even with paging enabled, when the average customer never navigates past the 2nd page. Most major shopping sites use this approach to speed up performance. For example, a good way is to mark a limited number of products as Featured products, therefore, showing only the subset of products when no category is being selected instead of showing all products. Likewise, sub-category is a great way to force customers to quickly narrow down to what they're looking for instead of paging through hundreds of pages. In general, aim for no more than a hundred products per category.
• Avoid creating unnecessary product variants when you can create product options with custom fields. Product variants are generally used when you need to track distinct inventory and SKU for each product option.
• Limit the use of product filter for only important attributes. Balance between speed and ease of navigation for your customers. Product filter is generally an intensive operation. Learn to take advantage of other forms of navigation filters like product search, category, manufacturer, distributor, etc.
• Reduce the number of unnecessary modules on your page that can clutter and slow down the page rendering.
• Set a small but reasonable limit on the number of results to show under Configuration > Product List and Configuration > Product Search settings. Study shows 80% of customers don't navigate past the 2nd page (e.g. 100 is a good limit). Rather than setting a high limit and expect the customer to click through 20 pages of products, you should emphasize the use of the product search module instead.
• Disable natural sort under Configuration > Product list settings. The natural sort algorithm is an expensive operation.
• Make sure your Log Level is set to "Error" mode under Configuration > General settings so that you're not logging unnecessary debug information.