Repository navigation
Stream S3 downloads and load tables in parallel - #47
Closed
shreyashankar wants to merge 1 commit into
Closed
shreyashankar wants to merge 1 commit into
shreyashankar wants to merge 1 commit into
Conversation
The download cache copied each S3 file through a random access file, which sends one HTTP range request per 64 KB read. Downloads ran at about 0.2 MB/s, so the scale factor 1.0 tables alone took about 20 minutes. The cache now reads a sequential stream, reuses one S3 filesystem, and load_benchmark fetches tables in parallel. A cold load at scale factor 1.0 takes 80 s and a warm one 6 s. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LnBPDnvaDsBDWZofvX25DU
shreyashankar
force-pushed
the
claude/faster-loading
branch
from
October 11, 2026 23:39
9ec67b0 to
fa6f8d2
Compare
Member
Author
|
Moved into #46. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
load_benchmarkwas very slow on a cold cache. Downloads ran at about 0.2 MB/s, so the 240 MB of scale factor 1.0 tables alone took about 20 minutes. The cause was in the download cache. It copied each S3 file through pyarrow's random access file, which sends one HTTP range request per 64 KB read. A 42 MB table took about 200 s to download, whilecurltook 6 s._cached_filereads a sequential stream with an 8 MB buffer.S3FileSystemis reused instead of a new one per call.load_benchmarkfetches its tables in parallel.Timing for
load_benchmark(scale_factor=1.0)on this branch's corpora:Corpus IDs, label IDs, and the way they are computed are unchanged. Ruff, the long-string check, vulture, and pytest pass.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LnBPDnvaDsBDWZofvX25DU