-
Notifications
You must be signed in to change notification settings - Fork 220
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
Summary table of likwid-perfctr shows incorrect values for "intensive" metrics #539
Comments
Thanks for your suggestion. I thought about it but it will not be in the upcoming 5.3 version. While the internal calculator would already support functions like In order to reduce the changes to the internal calculator, one could use a two-step approach. When creating the internal group structure, we could expand the proposed syntax Moreover, it does not change the way the statistics table is calculated and it is questionable whether it is still required at all. All threads would have the same CPI, Clock, etc. Calculating min, max, mean does not make sense for those or one has to magically transform |
Bug description
likwid-perfctr incorrectly reports some metrics by adding up core- or socket-local values. This happens, e.g., with:
These are "intensive" quantities, i.e., they do not scale with the size of the machine but need to be "averaged" (not literally, of course) in the proper way. In contrast, "extensive" quantities like energy consumption, memory data volume, etc, can be added across the machine to yield a useful number.
To Reproduce
likwid-perfctr -g MEM_DP -C M0:0@M1:0 likwid-bench -t triad_avx -W N:2GB:2
on dual-socket Ice Lake 6326Suggestion
The text was updated successfully, but these errors were encountered: