Skip to main content

Elasticsearch Memory Configuration (Windows)

New Windows deployments come with Elasticsearch, which by default uses 50% of server memory on initial installation. For a deployment on the minimum hardware, the suggested Elasticsearch allocation is 4 GB. These steps change the Elasticsearch memory allocation (up or down) on Windows.

The method for setting memory depends on your Informer version. For Elasticsearch deployments with Informer 2026.1.x and higher, memory is set in a heap.options file. For Elasticsearch deployments from Informer 2025.2.x and earlier, memory is set with the Elasticsearch service manager. Use the section that matches your version.

Informer 2026.1.x and higher​

In 2026.1.x and higher, set the allocation in the heap.options file.

  1. Stop the Informer Windows service.
  2. Stop the Elasticsearch Windows service.
  3. Open or create the jvm.options.d folder in the Elasticsearch config directory. For a server installed with Informer Setup, the path is: 
    C:\Entrinsik\Informer5 Server\elasticsearch\elasticsearch-X.x.x\config\jvm.options.d
    Replace X.x.x with your Elasticsearch version.
  4. Create a file named heap.options in that folder with these two lines. Replace 4g with your size. Set both values to the same size. 
    -Xms4g
    -Xmx4g
  5. Confirm the file is named heap.options and not heap.options.txt. Windows Explorer hides known extensions by default, so check the extension in the file properties or in a PowerShell listing.
  6. Start the Elasticsearch Windows service.
  7. Start the Informer Windows service.

For minimum-hardware deployments, use 4g.

Informer 2025.2.x and earlier​

  1. Stop the Informer Windows service. On a server built by the older console installer, also confirm in Task Manager that no Node.js processes remain, and end any that do.
  2. Open an elevated PowerShell and change to the Elasticsearch bin directory. For a server built by the older console installer, the path is under the Informer install root: 
    elasticsearch\elasticsearch-X.x.x\bin
  3. Launch the Elasticsearch service manager, passing your Elasticsearch service name (find it in the Windows Services manager, under the Elasticsearch service's properties): 
    .\elasticsearch-service.bat manager <serviceName>
  4. On the Java tab, set both Initial memory pool and Maximum memory pool to the same value. For minimum-hardware deployments, this is 4096 MB.
  5. Click OK, then stop and start the Elasticsearch Windows service to apply the change.
  6. Start the Informer service.