Reduce unneeded gh metadata #223
Draft
Conversation
This file contains 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
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.
Background
Four Keys queries in BigQuery and statistics on the Grafana dashboard take a long time time to run despite being uncomplicated. This is an attempt to reorganize the data sent to BigQuery in order to speed up performance.
Implementation Details
Reduction of the metadata inserted into tables in BQ from gh push and deployment-status actions. There are very few fields actually utilized in further reporting and cutting it down to these bare necessities can reduce the storage space required of the json metadata to ~25% it's original size (10.6MB -> 2.48MB).
Testing criteria
This is hard to test in a database environment until deployed, however nox unit testing can be performed on the code itself.
Jira Ticket
TBD