| Warning |
|---|
First of all : Do not underestimate the importance of SWAP memory ! Be sure your SWAP fits the recommandations according to your physical memory ! You can find recommandations in your operating system documentation and/or website |
The stability and performances of Datafari mainly rely on a good RAM management and distribution between its components. Adding more RAM to a Datafari server is completely useless if you don't configure it to exploit the available RAM !
...
Here are the files location and parameters that allow you to adjust the JVM RAM consumption by component :
| Component | File location | Parameter |
|---|---|---|
| Solr | DATAFARI_HOME/solr/bin/solr.in.sh | SOLR_JAVA_MEM (-Xms and -Xmx) |
| ManifoldCF | DATAFARI_HOME/mcf/mcf_home/option.env.unix | -Xms and -Xmx |
Tomcat | DATAFARI_HOME/tomcat/bin/statup.sh | CATALINA_OPTS (-Xms and -Xmx) |
| Cassandra | ||
| PostgreSQL |
| Elasticsearch | DATAFARI_HOME/elk/elasticsearch/config/jvm.options | -Xms and -Xmx |
| Logstash | DATAFARI_HOME/elk/logstash/config/jvm.options | -Xms and -Xmx |
| Kibana | DATAFARI_HOME/elk/scripts/set-elk-env.sh | NODE_OPTIONS (--max-old-space-size) |
| Tika server (Enterprise Edition) | DATAFARI_HOME/bin/start-tika-server.sh | TIKA_MEM (-Xms and -Xmx) |
| Info |
|---|
As a reminder, the "Xms" parameter defines the minimum amount of RAM consumption and the "Xmx" parameter the maximum ! It is highly recommended to have the same value for those two parameters. |
...