Closed GoogleCodeExporter closed 8 years ago
so by experimenting with likwid-perfctr, it appears that you are not using
UNC_L3_LINES_IN_ANY for the "MEM" group on Nehalem. So my comment would be to
fix the wiki page to reflect the actual status.
Curious to know -- what performance counters are used and why.
Thank you :)
Original comment by j...@hicampsystems.com
on 6 Jun 2011 at 2:56
Hi,
you can get a documentation with the exact events used for the derived metrics
with:
likwid-perfctr -g MEM -H
So just specify -g <GROUP> together with -H and you get the exact group setup.
So in the case of the MEM group this gives you:
Memory bandwidth [MBytes/s] =
1.0E-06*(UNC_QMC_NORMAL_READS_ANY+UNC_QMC_WRITES_FULL_ANY)*64/time
additionally there is a metric for the remote traffic:
Remote BW [MBytes/s]
1.0E-06*(UNC_QHL_REQUESTS_REMOTE_READS+UNC_QHL_REQUESTS_REMOTE_WRITES)*64/time
Thank for your WIKI error report, I will fix that.
You can get a list with all supported events with:
likwid-perfctr -e
If you encounter an error in a performance group or want to define your own
metrics you can easily do that, the groups are simple text files.
On Nehalem and Westmere likwid-perfctr supports ALL Uncore events. Support for
NehalemEX and SandyBridge Uncore is underway. Be careful for Uncore events as
they are always valid per socket and not per core if you are measuring
sequential applications.
Greetings,
Jan
Original comment by jan.trei...@gmail.com
on 14 Jun 2011 at 11:33
Original comment by jan.trei...@gmail.com
on 14 Jun 2011 at 11:34
Original comment by jan.trei...@gmail.com
on 29 Jul 2011 at 10:08
Original issue reported on code.google.com by
etep.nos...@gmail.com
on 5 Jun 2011 at 11:28