[MGNLTOMCAT-12] Aligning -Xms & -Xmx is a sane default Created: 09/Oct/19  Updated: 17/Oct/19  Resolved: 17/Oct/19

Status: Closed
Project: Barebones Tomcat Bundle
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Task DoD:
[ ]* Cloud deployments affected?
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

When Xms is low, off heap usage can grow while the JVM doesn't reach the Xmx value. As we have seen on client instances, when the instance is small, 100% off heap usage is reached quickly. At this point the JVM on one hand and the OS + Java libraries using native memory outside Java heap on the other compete for memory, leading to either of those eventually crashing.

Example of problematic values dissipating: https://github.com/magnolia-sre/magnolia-docker/pull/2/commits/58c4cacc53cf6dec1b040768a7592a5318dd78a6#diff-ca45d15dad8880b8ecfd1964e697bef7R15



 Comments   
Comment by Mikaël Geljić [ 17/Oct/19 ]

considering a "Won't fix" here; in the barebone we don't distinguish about the environment; as much as values are recommended to be aligned for production, they are also recommended to be kept distinct for development environments;

barebone itself is mostly used for the Magnolia CLI and for (demo) bundles; those rather fall into the second case, or am I missing an obvious production usage of this?

Comment by Maxime Michel [ 17/Oct/19 ]

This can be adressed by DEV-1366 indeed.

Generated at Sun Feb 11 23:26:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.