HomeGuidesAPI Reference
Submit Documentation FeedbackJoin Developer CommunityOptimizely GitHubOptimizely NuGetLog In

Optimizing Content Cloud performance

This topic describes strategies to run your Optimizely Commerce Cloud site at peak performance.

Optimizely Commerce performance depends on many factors. In general, an e-commerce site should perform well enough during peak times that each customer's shopping experience is fluid enough to convert their shopping cart to a sale. In addition, a site should perform well from small catalogs (50-100 products) to extremely large catalogs (100k+).

Consider the following strategies to run your site at peak performance.

Install the latest version of Optimizely Commerce

  • If possible, upgrade to the latest version of Optimizely Commerce, which includes performance improvements.

Strategies for large catalogs (300k+ entries)

  • Implement an enterprise-level search provider (like Solr), which can efficiently index a large catalog.
  • Eliminate or reduce the number of calls to the product catalog or database when returning product information during the browsing, search, or checkout process. Search is the critical element with large catalogs, because the return of search data to users determines response time.

Strategies for high volume/high load sites

  • Run performance tests prior to reaching peak times. Optimizely Commerce contains test scripts that you can modify to meet your scenarios and needs. You should spend as much time testing your application as implementing it.
  • Implement your Optimizely Commerce site in a load-balanced environment that can handle the expected traffic.
  • Consider a cloud-based hosting environment. Optimizely Commerce is tested in the cloud. This environment lets you easily and rapidly scale your infrastructure without having to invest in physical servers.
  • Implement fail-over or backup servers that can handle additional load.

Session state management

  • Enabling session states has noticeable overhead and can affect performance.
  • To reduce the overhead, only enable session state on pages that need it.

Did this page help you?