xarray-contrib / xarray-contrib/flox
Optimize `split_every`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 137
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
The split_every parameter controls how many blocks are combined at every combine stage.
If we know where the group labels are (so number of groups in a block, and number of elements in a group in each block), we can estimate memory use of the intermediates for a given reduction, and optimize split_every to reduce the graph size.
@mrocklin do you think this would be a decent win?
@tomwhite Is there a version of this in cubed?
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 reading the dask.array.reduction documentation for the split_every parameter and the issue's discussion of group labels, intermediate memory, and graph size. The issue does not name a flox file, test, or entry point, so the scope and completion criteria would need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100