Hardware requirements for HCL Commerce

The following reference provides a general guideline for the hardware capacity that is required for the HCL Commerce Version 9.1 release. This includes both full development and production environments for sites that are based on different sets of HCL Commerce solutions.

The primary technology that differentiates the hardware requirements for environments in HCL Commerce is the search solution. In general, it is observed that the Solr-based search solution requires fewer resources than the newer Elasticsearch-based solution. The resource requirements for the two supported storefront solutions are negligible and are therefore not stated outside of these general guidelines.

HCL Commerce development environment

Review the following table to ensure that the hardware capacity of your environment meets the recommended resource requirements. The following HCL Commerce development environment configurations include only those combinations which are deemed resource intense enough to state requirements.

Most stand-alone HCL Commerce Developer components (such as the HCL Commerce Developer Legacy environment and the HCL Commerce Developer React Store environment) do not have overly demanding resource requirements, and can be run on any typical modern development desktop or laptop.

To read more about the specific components included with the environments that are stated here, see Setting up an HCL Commerce development environment.

HCL Commerce Developer software combination Hardware capacity requirement
A full HCL Commerce development environment including:
  • The HCL Commerce Developer Legacy environment
  • The HCL Commerce Developer Tooling environment
  • The HCL Commerce Developer Search environment
  • The HCL Commerce Developer React Store environment
  • 8 CPU cores
  • 32 GB of memory
  • 120GB of free disk space
An HCL Commerce development environment for Elasticsearch-based search customization, which includes:
  • The HCL Commerce Developer Search environment
  • 6 CPU cores
  • 16 GB of memory
  • 100GB of free disk space

HCL Commerce Kubernetes production environment

Review the following table to ensure that the hardware capacity of your environment meets the recommended resource requirements. The following HCL Commerce production configurations include only those combinations which are deemed resource intense enough to state requirements.

To read more about HCL Commerce production configurations, see Setting up an HCL Commerce production environment. For more information about environment prerequisites specific to Kubernetes, see Prerequisites for deploying HCL Commerce on a Kubernetes cluster.

Ensure that your cluster has sufficient resources for your deployment. The requirements outlined below are only an estimate. They are based on a full environment (auth, live and shared groups) deployment with a single instance (replica set) for each application. These numbers also include the 10 vCPUs and 12GB of memory overhead requirement that are utilized in a rolling upgrade scenario. During an upgrade multiple instances of an application can be active at the same time.

The expected resources that are required are based on the search solution that is used in the deployment:
Search solution vCPUs Memory
Solr-based search solution 40 68 GB
Elasticsearch-based search solution 48 82 GB
Note:
  • The Elasticsearch Natural Language Processing (NLP) feature can consume large amounts of memory in NiFi with multiple languages enabled. For example, with two languages enabled, Nifi can use up to 10GB of memory. Ensure that adequate memory is allocated to Nifi for your deployment needs.
  • For a detailed breakdown on the suggested minimum Kubernetes resource requirements for a variety of deployment topologies, see HCL Commerce Kubernetes deployment resource planning.

HCL Commerce Docker-based production environment (for non-production usage)

Review the following table to ensure that the hardware capacity of your environment meets the recommended resource requirements. The following HCL Commerce production configurations include only those combinations which are deemed resource intense enough to state requirements.

To read more about HCL Commerce production configurations, see Setting up an HCL Commerce production environment. For more information about environment prerequisites specific to Docker, see Prerequisites for deploying HCL Commerce Version 9.1 with Docker Compose.

The expected resources that are required are based on the search solution that is used in the deployment:

Search solution Hardware capacity requirement
Solr-based search solution
  • 8 CPU cores
  • 16 GB of memory
Elasticsearch-based search solution
  • 8 CPU cores
  • 32 GB of memory