locationtech / locationtech/geomesa
Investigate reducing object allocation in arrow queries
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Investigate reducing object allocation in arrow queries
With larger batch sizes, Accumuo seems to hang with GC pauses. This may be due to the batch taking a while to compute, so things are moved to longer-term memory, which causes more GC work. Still, minimizing object creation should help regardless of batch size.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2104
Key: GEOMESA-2104
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Mon, 11 Dec 2017 17:44:13 -0500
Updated: Mon, 11 Dec 2017 17:44:13 -0500
Affects Version(s): 1.3.5
Contributor guide
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 with the Arrow query path and reproduce the reported GC pauses using larger batch sizes in Accumulo. Profile object allocation during query computation, then validate that any identified reduction improves allocation or GC behavior without changing query results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100