3.35.2.6: Sorting: 157 tracks, sort by Closest, 34s on new tablet....
My times are massively higher, as I have tons of data from recent years.
Questions to Menion:
- did you introduce the bounding boxes for tracks that we discussed months ago (min/max in each dimension, as part of the track data model) ?
- computing the distance of a point to any bounding box rectangle (representing a track) is a simple formula rather than traversing 1000s of points
- if you then limit the number of items for the result (like your "first 10, 25, 100, ... or so in other places of Locus) the search will be really fast, as you get the right "candidates" cheaply.
Maybe you do such already, but the high amount of tracks is still killing. In particular as there are no restrictions to a folder or so, right ?
TXs and cheers
Michael