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
We got some feedback that this top bar was confusing to some users. Heba has some ideas for how to improve it.
While we are at it, we should also think about how to present this information when we have
more than one machine type, and
more than one timeout value
For example, in the next benchmark run, we plan to run the R sized benchmarks on a larger machine with a larger 10h timeout. The existing benchmarks will be run on the existing machine with a 1h timeout.
Perhaps one idea is to have tabs on the top of the dashboard so that the user can select between smaller benchmarks and real-sized benchmarks. This will also simplify the SGM calculation, as each "tab" will use a single TO/ER value for runtime.
The text was updated successfully, but these errors were encountered:
We got some feedback that this top bar was confusing to some users. Heba has some ideas for how to improve it.
While we are at it, we should also think about how to present this information when we have
For example, in the next benchmark run, we plan to run the
R
sized benchmarks on a larger machine with a larger 10h timeout. The existing benchmarks will be run on the existing machine with a 1h timeout.Perhaps one idea is to have tabs on the top of the dashboard so that the user can select between smaller benchmarks and real-sized benchmarks. This will also simplify the SGM calculation, as each "tab" will use a single TO/ER value for runtime.
The text was updated successfully, but these errors were encountered: