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
Additional scenarios. We currently have a list of scenarios that we've developed for parity with the old "Bench" performance framework, which is what's currently displayed on the OpenDDS "performance" website. We'd like for the performance dashboard to support displaying these scenarios as well as the ones we've currently developed. In combination with the next point, we could then have the OpenDDS performance page point to the current set of performance metrics for the most recent release and/or master branch.
The text was updated successfully, but these errors were encountered:
Making a few notes on this. There are multiple parts to this.
Being able to display the stats from the new scenarios. This is already supported and currently viewable.
Being able to do comparisons between scenarios, which is partially done (latency and jitter only) as part of the legacy bench results for the old performance web page. This is not currently supported.
The last part, which will require more back-end work for bench, is being able to display certain collections of statistics as time-series (or histogram) data. This is not currently supported, and would require more work on the bench backend to get up and running.
simpsont-oci
changed the title
Accommodate New Scenarios
Visualization Parity with Legacy Bench Results
Sep 1, 2022
Additional scenarios. We currently have a list of scenarios that we've developed for parity with the old "Bench" performance framework, which is what's currently displayed on the OpenDDS "performance" website. We'd like for the performance dashboard to support displaying these scenarios as well as the ones we've currently developed. In combination with the next point, we could then have the OpenDDS performance page point to the current set of performance metrics for the most recent release and/or master branch.
The text was updated successfully, but these errors were encountered: