https://community.denodo.com/kb/en/view/document/Denodo%20Admin%20and%20Development%20Best%20Practices
https://community.denodo.com/kb/en/view/document/Denodo%20Best%20Practices%20and%20Guidelines
-- 1. JVM Configuration
it is not recommended to use a heap size greater than 16 Gb
the recommended settings for the JVM can be directly set from the VQL shell:
SET 'java.env.DENODO_OPTS_START' = '<JVM settings>';
-- 1.1 Recommended settings for the JVM in memory-demanding scenarios
-server -Xms8192m -Xmx8192m -XX:+DisableExplicitGC -XX:+UseG1GC -XX:ReservedCodeCacheSize=256m
-- 1.2 Recommended settings for the JVM in real time scenarios
-server -Xms4096m -Xmx4096m -XX:+DisableExplicitGC -XX:+UseG1GC -XX:MaxGCPauseMillis=1000 -XX:ReservedCodeCacheSize=256m
-- 2. System Memory Management
By default, glibc uses a total amount of 8*number_of_cores memory pools when reserving memory
and this consumes too much space in the JVM.
To minimize the memory usage
it is possible to set an environment variable in the system called MALLOC_ARENA_MAX.
export MALLOC_ARENA_MAX=<2 x (# ofCPU Cores)>
-- 3. Cache Configuration
use the following external RDBMSs to store the cache: MySQL, Oracle or MS SQL Server.
