Performance · AMP
Optimizing Liferay DXP Performance & JVM Tuning
Optimize Liferay DXP performance by sizing JVM heap to 8-16GB, selecting G1GC/ZGC garbage collectors, tuning Hikari database connection pools, enabling CDN page cache, and compressing CSS/JS files.
How Do You Configure JVM Settings to Speed Up Liferay DXP?
Direct Answer: Tune Java virtual machine startup flags, setting equal min/max memory sizes and using advanced garbage collectors like G1GC.
Liferay is built on Java. Sizing heap allocation incorrectly creates garbage collection bottlenecks. Apply optimal JVM flags, forcing identical Xms/Xmx values and activating GC log files to audit memory cycles.
# Optimal GC flags for G1GC
-Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=200
Proper memory configuration prevents JVM resize latency and keeps garbage collection pauses under 200ms, stabilizing portal speeds.
Hikari CP Sizing
Size your database pool. Set Hikari connections relative to expected threads, avoiding database lock issues during search indexing. Configure database indices to speed up queries.
CDN Resource Caching
Offload static files (images, css, javascript) to CDNs. This reduces hits on Liferay nodes, letting portal engines focus on assembling pages and serving authenticated API requests.
Frequently asked questions
Is ZGC better than G1GC for Liferay?
Yes. ZGC keeps garbage collection pause latency under 1ms, preventing portal timeouts and scaling smoothly for large heaps.
Should we cache html files in the CDN?
Cache layouts with short TTLs. Force query checks for authenticated sections to prevent session leaks.
Read the full article, with table of contents, comparison table, and author bio →