mapdb
mapdb copied to clipboard
Memory limits for compaction to work
I run java service with Xms1G and Xmx2G. My mapdb file is 1.4G. Compaction fails with java.lang.OutOfMemoryError: Java heap space. While the solution here would be to increase Xmx to probably 4G it's interesting what limitations are expected for memory consumption. Like, what memory ranges are OK when DB size is XG, YG or ZG. Or maybe it's possible to avoid OOM even for small services and large DBs.
Compaction should not use too much heap. Will investigate
The latest here: 5.8GB mapdb file and 10G Xmx result into java heap space OOM...