Remove no-branch from release dashboard - #774
Open
hugovk wants to merge 1 commit into
Open
Conversation
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
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.
Does anyone use the no-branch section of the release dashboard?
If not, let's remove it. This would save fetching data for 142 of the 1,074 builders listed on the page, about 13%.
A cached page takes about 2s:
Forcing a refresh:
ttfb is time to first byte, and tells us when the page has already finished querying all the data it needs, so this is roughly about how long it takes to run on the server.
Dropping no-branch would bring that to about 22s, and also save about 0.9 MB of the 13.2 MB HTML page.
The cron to refresh this page is every 5 mins so it's 12 times per hour:
https://github.com/python/psf-salt/blob/05305dee04372ad00c4dd66fca14ab13e35754f3/salt/buildbot/init.sls#L99-L103