EGO_DISTRIBUTION_INTERVAL
|
ego.conf
|
Improves container startup speed, client response time, and overall cluster performance. The default is 5.
Example:
EGO_DISTRIBUTION_INTERVAL=1
|
EGO_ENABLE_COMPRESS_STATUS_FILE
|
ego.conf
|
Improves VEMKD file operation performance, thereby improving client response time and overall cluster performance. The default is "N".
Example:
EGO_ENABLE_COMPRESS_STATUS_FILE=Y
|
EGO_DYNAMIC_HOST_WAIT_TIME
|
ego.conf
|
Provides compute hosts with a greater chance to be recognized by the master host. The default is 60.
Example:
EGO_DYNAMIC_HOST_WAIT_TIME=60,120
|
EGO_DATA_MAXSIZE
|
ego.conf
|
Specified in Mbytes. Reduces the frequency for VEMKD to swtitch the stream file, to give the PERF loader sufficient time to finish loading data from the file to the database. Note: Adjust this parameter in conjunction with PERF egoeventsloader interval. The default is 10.
Example:
EGO_DATA_MAXSIZE=100
|
egoeventsloader->Interval
|
plc_ego.xml
|
Specified in seconds. Sets the interval shorter than the VEMKD stream file switch time so that the loader is able to load all data in the stream file before VEMKD switches it. Note: Adjust this parameter in conjunction with EGO_DATA_MAXSIZE in ego.conf.
Example:
<DataLoader Name="egoeventsloader" Interval="300" Enable="true" LoadXML="dataloader/egoevents.xml" />
|
EXINTERVAL
|
ego.cluster.<clustername>
|
Provides VEMKD with a greater chance to obtain load information from the master lim.
Example:
EXINTERVAL=150
|
MEM_HIGH_MARK and JAVA_OPT
|
wsm.conf
|
Reduces the chance of WEBGUI service restarts in a large cluster, and also helps with generating PERF reports.
Example:
MEM_HIGH_MARK=2048
JAVA_OPTS="-Xms512m -Xmx2048m"
|
Java maximum heap size
|
EGO_TOP\perf\1.2.5\etc\plc.bat (Windows)
EGO_TOP/perf/1.2.5/etc/plc.sh (Linux)
|
Gives more memory to the PLC service for collectiing data in a large cluster.
Example: (Windows)
"%JAVA_HOME%\bin\java.exe" -Xms64m -Xmx2048m ...
|
<ReclamationTimeout>
|
ConsumerTrees.xml
|
Reduces the chance of forcible reclaim happening.
Example:
<ReclamationTimeout>300</ReclamationTimeout>
|
EGO_MAX_CONN
|
ego.conf
|
Consider this only when there are more than 5000 physical hosts in a cluster. This configuration allows VEMKD to maintain more connections.
Example:
EGO_MAX_CONN=20000
|
SSM > startUpTimeout
|
Application profile
|
When there are many applications (e.g=. 300) in a cluster, SD may not be able to register all applications when many applications start SSM at the same time within the default SSM startUpTimeout. Consequently, some SSM processes may exit due to startup timeout. The default is 60 seconds. Increase this setting in a cluster with many applications. 300 seconds is suggested for clusters with 300 applications.
Example:
<SSM resReq="" workDir="${EGO_SHARED_TOP}/soam/work" startUpTimeout="300" shutDownTimeout="300">
|