task.mem should be set to use jvmargs that pin the min and max heap size [LUCENE-2009]
Open
affects-version:2.9
legacy-jira-priority:Minor
module:benchmark
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Currently, task.mem sets the java ant task param maxmemory - there is no equivalent minmemory though. jvmargs should be used instead, and xms,xmx pinned to task.mem - otherwise, results are affected as the JVM resizes the heap.
---
Migrated from [LUCENE-2009](https://issues.apache.org/jira/browse/LUCENE-2009) by Mark Miller (@markrmiller), updated Nov 30 2013
Contributor guide
Research direction
Search the build configuration for task.mem and the Java Ant task parameters; start by comparing the current maxmemory setting with the requested jvmargs behavior. Done means task.mem supplies matching minimum and maximum heap settings so JVM heap resizing cannot affect results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100