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
The common form of Index introduced in Car V2 is to lay out the CIDs in the car in a sorted table that can be quickly walked through with a binary search.
We should attempt to optimize not fully copying the index into memory when loading a car, and just doing spot reads from the index. This can for large cars avoid a copy of hundreds of megs per individual block read.
The text was updated successfully, but these errors were encountered:
Dupe of #243 or #95, perhaps. We already have multiple issues that all boil down to: we should be able to consume some index formats directly from disk.
yep, happy to dupe, maybe this is more trying to indicate that this remains one of our expected performance bottle necks that we shouldn't lose track of
The common form of Index introduced in Car V2 is to lay out the CIDs in the car in a sorted table that can be quickly walked through with a binary search.
We should attempt to optimize not fully copying the index into memory when loading a car, and just doing spot reads from the index. This can for large cars avoid a copy of hundreds of megs per individual block read.
The text was updated successfully, but these errors were encountered: