locationtech / locationtech/geotrellis
Bad performance with ZSpaceTimeKeyIndex
Open
Nobody has claimed this yet.
bug
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 360
- Avg merge
- 6h 57m
- Merged PRs (30d)
- 12
Description
Is your feature request related to a problem? Please describe.
Bad performance when computing indexRanges with geotrellis.store.index.zcurve.ZSpaceTimeKeyIndex
Describe the solution you'd like
A faster way to compute indexRanges
Describe alternatives you've considered
I tried using org.locationtech.sfcurve.zorder.Z3.zranges instead and it looks like performance is a lot better.
Example:
// took me 50 seconds
geotrellis.store.index.zcurve.Z3.zranges(17592186191908, 17597546219268)
// ran in 2.5 seconds
org.locationtech.sfcurve.zorder.Z3.zranges(Array(ZRange(17592186191908, 17597546219268)), maxRecurse = Some(11))
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 geotrellis.store.index.zcurve.ZSpaceTimeKeyIndex and its indexRanges implementation, then inspect geotrellis.store.index.zcurve.Z3.zranges. Compare it with org.locationtech.sfcurve.zorder.Z3.zranges using the issue's example range and timing. Done means indexRanges computes equivalent ranges with substantially better performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100