feat: use Storage Read API for faster data fetching #1368
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.
Depends on googleapis/nodejs-bigquery-storage#431
Some early results:
SELECT repository_url as url, repository_owner as owner, repository_forks as forks FROM `bigquery-public-data.samples.github_timeline` where repository_url is not null LIMIT 300000
31.135s
🔴20.033s
⬆️ 36% speedupSELECT repository_url as url, repository_owner as owner, repository_forks as forks FROM `bigquery-public-data.samples.github_timeline` where repository_url is not null LIMIT 1000000
1:32.622
(m:ss.mmm) 🔴1:07.363
(m:ss.mmm) ⬆️ 27% fasterSELECT name, number, state from `bigquery-public-data.usa_names.usa_1910_current
5:00.514
(m:ss.mmm) 🔴3:20.987
(m:ss.mmm) ⬆️ 33% faster