Benchmarks: lance file format for dependency table #425
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the comment in #424, I benchmarked
lance
as a file format for storing the dependency table.Results for writing 1000000 lines.
Results for reading 1000000 lines.
As can be seen, reading speed is only better if we read to an
lance.LanceDataset
object. Which means we also need to check, how the dependency table methods would behave when directly working on a lance dataset.NOTE: results are not yet added to the README