Skip to content

Reduce key node version granularity to major releases only #1986

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
kevinschaper wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Reduce key node version granularity to major releases only #1986

kevinschaper wants to merge 2 commits into from

Conversation

@kevinschaper
Copy link
Contributor

@kevinschaper kevinschaper commented Dec 9, 2025 •
edited
Loading

Summary

  • Filter release trends queries to only include major releases (x.y.0), the benchmark version, and the current release version
  • Reduces the number of versions scanned from 61 to ~10
  • Estimated ~84% reduction in BigQuery bytes processed for key node queries that are per-release, based on linear scaling assumption

Test plan

  • Verified script generates SQL with only 10 versions instead of 61
  • Confirmed generated SQL file reduced from 3326 lines to 551 lines
  • Verify dashboard builds successfully and visualizations look correct

🤖 Generated with Claude Code

@kevinschaper @claude
Reduce key node version granularity to major releases only
87ffc9c 
Filter release trends queries to only include major releases (x.y.0),
the benchmark version, and the current release version. This reduces
the number of versions scanned from 61 to ~10, providing an estimated
~84% reduction in BigQuery bytes processed (~260 GB savings per query).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@kevinschaper
Copy link
Contributor Author

kevinschaper commented Dec 9, 2025

Alzheimer Disease
Screenshot 2025-12-09 at 12 59 31 PM
Castelman Disease:
Screenshot 2025-12-09 at 12 59 48 PM

Looks fine!

@kevinschaper kevinschaper marked this pull request as ready for review December 9, 2025 21:01
@kevinschaper kevinschaper requested a review from a team as a code owner December 9, 2025 21:01
@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2026

This pull request has been automatically marked as stale because it has had no activity in the last 14 days.

If this PR is still relevant:

  • Please update it to the latest main/master branch
  • Address any existing review comments
  • Leave a comment to keep it open

Otherwise, it will be closed in 2 weeks if no further activity occurs.

@github-actions github-actions bot added the stale label Jan 2, 2026
JacquesVergine
JacquesVergine approved these changes Jan 5, 2026
View reviewed changes
Copy link
Collaborator

@JacquesVergine JacquesVergine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work thanks Kevin!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JacquesVergine JacquesVergine JacquesVergine approved these changes

@pascalwhoop pascalwhoop Awaiting requested review from pascalwhoop

Assignees

No one assigned

Labels

stale

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kevinschaper @JacquesVergine @Dashing-Nelson