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
{{ message }}
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.
My suggestion is to add all core benchmarks to the build setup but run them once a month. Since running all the benchmarks takes multiple days, it would be crazy to run them nightly. With monthly setup we can have complete performance data and overtime we can get a trend line. There is still a problem of presenting this data accurately without overwhelming the users and gain understanding of the performance trend. It would be really helpful to get some feedback from the community mainly contributors for the benchmarking team.
The text was updated successfully, but these errors were encountered:
My suggestion is to add all core benchmarks to the build setup but run them once a month. Since running all the benchmarks takes multiple days, it would be crazy to run them nightly. With monthly setup we can have complete performance data and overtime we can get a trend line. There is still a problem of presenting this data accurately without overwhelming the users and gain understanding of the performance trend. It would be really helpful to get some feedback from the community mainly contributors for the benchmarking team.
The text was updated successfully, but these errors were encountered: