Consider changing heuristic for number of chunks
- Dominant language
- Java
- Stars
- 94
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
@StephanPreibisch says that it is somehow much more efficient to use `numElements / numThreads / 3` rather than simply `numElements / numThreads`, in places [like this](https://github.com/imagej/imagej-ops/blob/imagej-ops-0.5.0/src/main/java/net/imagej/ops/chunker/DefaultChunker.java#L66) and [this](https://github.com/imagej/imagej-ops/blob/imagej-ops-0.5.0/src/main/java/net/imagej/ops/chunker/InterleavedChunker.java#L64).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the chunk-count calculations at the referenced lines in src/main/java/net/imagej/ops/chunker/DefaultChunker.java and InterleavedChunker.java. Compare the current numElements / numThreads heuristic with the proposed division by 3, then determine how the chosen heuristic should be validated. Done means the intended chunk calculation is agreed and consistently updated in the affected locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100