You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
issues #904 reminds me about the follow ideas we have informally disucssed internally.
right now, most of our integration tests are feature-oriented, i.e. they are designed to cover a dash feature. But we don't have a metrics system to track some core performance such as handling of callbacks, a significant chunk of data to be loaded in dcc.Graph or dash-tables.
So we can get an alert if one release candidate slows significantly comparing to previous versions.
Describe the solution you'd like
We need to design a set of scenarios to test load/performance of dash
We can get the execution time from pytest junit reports. they are either stored in cirlceci or we can report and archive them after each run in a DB
we can then compare each time when a new record is reported with a threshold to trigger such alert that the last change has broken the performance
we can also leverage the existing performance toolchain on js side like pupeeter and lighthouse.
Activity
[-][Feature Request][/-][+][Feature Request] Performance benchmark tests[/+]Merge pull request plotly#907 from plotly/dash-1506
Merge pull request #907 from plotly/dash-1506
Merge pull request #907 from AnnMarieW/fix-pagination
[-][Feature Request] Performance benchmark tests[/-][+]add performance benchmark tests[/+]AnnMarieW commentedon Sep 11, 2026
closed by #3954