Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

sperf gc time shift #2

Open
rsds143 opened this issue Jan 27, 2020 · 0 comments
Open

sperf gc time shift #2

rsds143 opened this issue Jan 27, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@rsds143
Copy link
Contributor

rsds143 commented Jan 27, 2020

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

@rsds143 rsds143 added the bug Something isn't working label Jan 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant