Performance Budgets are an effective way of making sure regressions in performance are noticed and addressed quickly. You can set Budgets against every metric in Calibre. This article explains how to create a performance budget successfully, their types, and notifications associated with budgets.
Start by selecting a metric to track. Once you choose one, the chart below populates with historical tracking information (if present), and how frequently specific measurements occur. The highest bars mean the most common reading. The chart is re-generated each time you select specific Pages or Test Profiles.
The chart is colour-coded accordingly to Slow, Average and Fast range recommendations (for timing-based metrics) or Small, Average and Large recommendations (for byte size-based metrics).
With this context, you can select a Budget value that is informed by your use case but also meets recommendations for best performance.
You can set the same Budget for all, one or a custom selection of Pages within a given Site. Once you choose Select Pages, you will see a list of all Pages in your Site.
It’s possible to set a single Budget against all Test Profiles in use. You can also set separate Budgets for each Test Profile. Since different Test Profiles produce varying monitoring data, it’s important to track Budgets for them separately.
We recommend setting separate Budgets when dealing with vastly different environment set-ups, such as Desktop with Cable connection, Motorola Moto 3G or turning off ads and third parties.
By default, Calibre won’t send any notifications when a Budget is created. Anyone with access to a given site can subscribe to Budget notifications in their Email Notification Settings.
If turned on, you will receive a notification each time there is a persistent change to the overall Budget status. This highlights changes persisting in the long term instead of observing monitoring fluctuations that are normal in monitoring scenarios.
A performance budget can be in one of three states:
If using Pull Request Reviews, you can opt in to fail the pull request check if an existing performance budget is not met in the tested pull request.
On this page