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 Jan 19, 2022. It is now read-only.
When using sperf core gc to evaluate a subset of nodes, and start and end times, the output provides the incorrect busiest period. It includes the busiest_period output from all of the nodes. Nothing major since you print the gc histogram correctly - but if someone copies/pastes the gc output in a customer ticket - it won't line up correctly.
via Richard Hamlin
The text was updated successfully, but these errors were encountered:
When using sperf core gc to evaluate a subset of nodes, and start and end times, the output provides the incorrect busiest period. It includes the busiest_period output from all of the nodes. Nothing major since you print the gc histogram correctly - but if someone copies/pastes the gc output in a customer ticket - it won't line up correctly.
via Richard Hamlin
The text was updated successfully, but these errors were encountered: