feat(timings): add 90d, 6mo, and 1y time ranges#442
Merged
Conversation
Long ranges fetch the lightweight daily winrate aggregation (fct_engine_new_payload_winrate_daily) instead of the hourly and per-slot tables, which are too heavy at this scale. The winrate chart renders one normalized stacked bar per day, while hourly-backed sections show an explicit unavailability note.
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.
Adds Last 90d / Last 6mo / Last 1y ranges to the Engine API Timings page. Long ranges fetch the tiny daily winrate aggregation (fct_engine_new_payload_winrate_daily) instead of the hourly and per-slot tables, rendering one normalized stacked bar per day with standings computed from grand-total win counts. Sections that depend on hourly or per-slot data show a small "Not available for ranges beyond 31 days" note instead of empty charts.