You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're putting fixing this on hold due to other priorities, but it should be documented.
Currently, a batch read will enumerate the buckets it hits O(n) times in the number of points read/read each point O(n^2) times, due to naive filtering out of points which aren't the one being currently read. This can be fixed by only reading each bucket once per batch (either memoize it, or rethink the intermediate datastructure used to accumulate points in a request).
The text was updated successfully, but these errors were encountered:
We're putting fixing this on hold due to other priorities, but it should be documented.
Currently, a batch read will enumerate the buckets it hits
O(n)
times in the number of points read/read each pointO(n^2)
times, due to naive filtering out of points which aren't the one being currently read. This can be fixed by only reading each bucket once per batch (either memoize it, or rethink the intermediate datastructure used to accumulate points in a request).The text was updated successfully, but these errors were encountered: