The Denodo Platform has the following hardware requirements:
For simple scenarios: Intel Xeon quad-core or similar.
For high-load scenarios or cases with complex calculations: 8 cores or more.
|Physical memory (RAM)||16 gigabytes of memory so the Denodo server components can allocate a runtime heap space up to 8 gigabytes.|
Minimum: 5 gigabytes
Recommended: 10 gigabytes
Recommended for very complex scenarios involving billions of rows: 100 gigabytes.
See the explanation below.
|For a High-Availability configuration, an external load-balancer.|
The Denodo Platform can be installed on a virtual machine with similar characteristics, provided that equivalent resources are permanently allocated.
It is very important to avoid memory overcommitment. That is, the amount of memory assigned to the virtual machine has to be backed by physical memory. Otherwise, the host operating system will have to swap to disk parts of the virtual | machine. This will lead to a severe decrease of the performance of the Denodo Platform.
For more advice regarding sizing, contact the Denodo Support Team.
Recommendations when Running Denodo on Amazon AWS¶
In the following table, find the recommended instance types of Amazon AWS to run the Denodo Platform:
|Recommended instance type||General Purpose instance of type M|
|Recommended minimum for production servers||m4.xlarge or m5.xlarge|
|Recommended for production servers in very complex scenarios||
m4.4xlarge or m5.4xlarge
On scenarios where Denodo executes very complex queries, these instances provide significant performance improvements over less powerful instances. More powerful instances (e.g. m4.10xlarge, m5.10xlarge) may be beneficial with some workloads but the improvement is usually smaller.
Recommendations when Running Denodo on Microsoft Azure¶
In the Denodo page of the Microsoft Azure Marketplace, the tab Plans + Pricing lists the instance types we recommend to run the Denodo Platform.
Disk Space Requirements of the Denodo Platform¶
The amount of free disk space required depends on the use of the Denodo Platform:
A full installation of the Denodo Platform (i.e. installation of all the modules: ITPilot, Scheduler and Virtual DataPort) uses 1.5 gigabytes.
The metadata of each module of the Denodo Platform is stored locally (e.g. information about the data sources, views, web services, Scheduler jobs, etc.) and usually does not go over a few hundred megabytes.
Space used by updates: Denodo keeps a backup copy of the libraries that are being updated. Each update takes up to 300 megabytes. Considering the number of updates released per each major version, the backup copies end up using around 5 gigabytes.
Space used for swapping data: to avoid memory overflows, Virtual DataPort swaps to disk the intermediate results of queries when they do not fit in memory.
Usually, most of the processing is pushed down to the source so the number of rows processed by Virtual DataPort is low and swapping is not required. However, with very complex queries where Virtual DataPort processes billions of rows, some data is swapped to disk to avoid a memory overflow. This is why, for complex scenarios, we recommend having 100 gigabytes of free disk space.
The section Memory Management of the Virtual DataPort Administration Guide explains when Virtual DataPort swaps intermediate results to disk.