Memory limits for compaction to work
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.1k
- Forks
- 877
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing compaction with the reported 1.4G MapDB file and Java heap settings of Xms1G/Xmx2G. Measure memory use across database and heap sizes, then document the expected limits or whether compaction can avoid OutOfMemoryError for large databases on small services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100