Opening an application to visualize charts through the hub, the visualization may fail and the error "Out of calculation memory" will be printed.
Environment:
Qlik Sense Enterprise on Windows, all versions
Resolution
The issue is often related to having an app that is too large or requires a re-design or general optimization. A poorly designed application can lead to memory leaks.
Application optimization
Review the application and optimize as needed to prevent performance problems for the engine service.
Verify resource availability
Verify that the servers hosting the Qlik Sense engine service have sufficient resources (CPU / Memory) to proceed with the calculation. It is highly recommended to have at least 16 cores and 64 GB of memory.
Modify the Hypercube memory limits (bytes). This is by default set to 0, which allows the engine to apply a global heuristic ensuring that we do not run more than 1 big calculation in parallel. Setting this value to -1 will disable the limit.
Restart the Qlik Sense Engine and Qlik Sense Service Dispatcher on all nodes after the setting was changed.
Cause:
The "Hypercube memory limits" limits how much memory a hypercube evaluation can allocate during a request. If multiple hypercubes are calculated during the request, the limit is applied to each hypercube calculation separately.
If it sets to 0, the engine applies a global heuristic which basically ensures that it doesn't run more than 1 "big" calculation in parallel. If you set this value to -1 then you will disable the limit and allow the Engine to keep trying to load the application.
The negative value disables the limit, but it wouldn't exceed the limit set under the Max memory usage (%) or Memory usage mode.