...
5. Add the following setting to wcs-core.properties (for example, allocating 24G under memory heap):
- in JDK 12-15
| Code Block | ||||
|---|---|---|---|---|
| ||||
# ZGC
-XX:+UnlockExperimentalVMOptions -XX:+UseZGC -Xms24g -Xmx24g |
- in JDK 16 and newer
| Code Block | ||||
|---|---|---|---|---|
| ||||
# ZGC -XX:+UseZGC -Xms24g -Xmx24g |
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
sysctl -w vm.max_map_count=131072 |
and restart WCS.
Known issues
1. CPU load average is higher when ZGC is used, especially in JDK 15
Symptoms: CPU load average measured at system level (using htop for example) grows after update from JDK 12 or 14 to 15 if ZGC is used
Solution: use ZGC in JDK 12 or 14 only fro high loaded servers if GC pauses minimizing is required
2. ZGC logs may occupy a huge disk space with default output configuration
Symptoms: gc-core*.log files occupy a huge disk space
Solution: limit log tags set to write to GC logs with the following parameter in wcs-core.properties
| Code Block | ||
|---|---|---|
| ||
-Xlog:gc,gc+start,gc+phases:/usr/local/FlashphonerWebCallServer/logs/gc-core-:time |