4 ms·
One project I worked on recently ran on containers with 256MB memory, on k8s. Main app would use ~80MB, plus five or six sidecars for metrics, logging, discover
by jiofih 5y ago
One project I worked on recently ran on containers with 256MB memory, on k8s. Main app would use ~80MB, plus five or six sidecars for metrics, logging, discovery, http proxy etc using 5-10MB each. Having a 100MB+ baseline makes it prohibitive for most of those applications.
- kaba0 5y agoThe JVM's memory usage is based on a heuristic. It can get away with usually much less, but it errs on the bigger memory footprint side, because that way it has to do less actual work GC-wise. For example, anecdotally a small, semi-complex JavaFX 2D game I wrote uses by default something like 250 MiB of RAM, but manually limiting it to max 80 was possible (but in the latter case, the GC had to run quite often)