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
Track cache misses from perf counters. #370
Comments
|
So |
In theory I believe this is the list of performance counters on the collection machine -- @eddyb , would you be willing to look through that and select a few that would fit the "cache misses" bit? I suspect that maybe "cache-misses" is enough though we may want to actually split into more specific data... |
My guess would be Comparing |
https://gist.github.com/Mark-Simulacrum/151b4948d6bd1ab86b5c1d9b36ba64de is the current output of |
Cache misses are now tracked and stored in the DB. And we're running out of HW counters (I think that there's only one left now), so I'm not sure if it's worth it to add some more detailed cache miss metric here. |
Cache misses are now tracked, so I think that this can be closed. |
Cache misses should correlate strongly with DRAM accesses, so they should give us a good measure of "time wasted because of memory usage/non-locality".
Not sure why we track "faults", but if that is available, cache misses would be too, I presume?
The text was updated successfully, but these errors were encountered: