-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show Aggregated Perf Results in Perf Graph View #106
Comments
We should break this into several steps:
|
- Based on ODM.jsx, added a perf graph for AcmeAir - Added parsers for adding information to Node version Issue adoptium#119 Issue adoptium#106 Signed-off-by: Jiayao Lin <jiayaolinn@gmail.com>
- Based on ODM.jsx, added a perf graph for AcmeAir - Added parsers for adding information to Node version Issue adoptium#119 Issue adoptium#106 Signed-off-by: Jiayao Lin <jiayaolinn@gmail.com>
- Based on ODM.jsx, added a perf graph for AcmeAir - Added parsers for adding information to Node version Issue adoptium#119 Issue adoptium#106 Signed-off-by: Jiayao Lin <jiayaolinn@gmail.com>
- Based on ODM.jsx, added a perf graph for AcmeAir - Added parsers for adding information to Node version Issue adoptium#119 Issue adoptium#106 Signed-off-by: Jiayao Lin <jiayaolinn@gmail.com>
Only ODM and AcmeAir graphs are updated to use aggregated perf results. Liberty and SPECjbb2015 graphs haven't been updated. Since we aren't really using any perf graphs for perf monitoring due to their current limitations, we can probably fix those after working on #118, not requiring any special changes for them. |
Problem Description
With #73, we've added the ability to aggregate the perf results from multiple iterations. We should update Perf Graph View to use and display aggregated perf results in order to comply with the new design.
Proposed Changes
Besides the info that's already displayed, show all aggregated data for each build:
Assigned Contributors
I'll be working with Sophia (@sophiaxu0424) from my team to add this feature.
The text was updated successfully, but these errors were encountered: