The countdown from eeeslab

View Code? Open in Web Editor NEW

COUNTDOWN is a tool for identifying and automatically reducing the power consumption of the computing elements during MPI communications.

License: BSD 3-Clause "New" or "Revised" License

CMake 2.56% C 97.44%

countdown's People

Contributors

Stargazers

Watchers

countdown's Issues

Events' information is missing

Hi,

It seems that the current version dd66063 does not provide an output of the events that are being monitored. A working instance seems to be on (4 of August 2022): 74dde21. Both cases have been tested with the same configuration (i.e. env variables).

Env variables:

export LD_PRELOAD=/<path>/countdown/build/src/libcntd.so

export CNTD_DISABLE_POWER_MONITOR=on
export CNTD_PERF_ENABLE=on

# For each perf event
codes=(0xc4 0xc5 0x8108 0x149 0x412e 0x110 0x185)
for i in "${!codes[@]}"; do
        export CNTD_PERF_EVENT_$i=${codes[$i]}
done

export CNTD_ENABLE_REPORT=on
export CNTD_ENABLE_TIMESERIES_REPORT=on

The current version creates an output that contains:

...
MAX Memory usage:   	192.06 MByte
AVG IPC:            	1.46
AVG CPU frequency:      0 MHz
Cycles:                 352587934310
Instructions retired:   513596918758
##################### MPI TIMING #####################
APP time: 125.694 sec (99.04%)
MPI time: 1.221 sec (0.96%)
TOT time: 126.915 sec (100.00%)
##################### MPI REPORTING ##################
...

While the older commit creates an output that contains:

...
MAX Memory usage:   	189.16 MByte
AVG IPC:            	1.46
AVG CPU frequency:      2800 MHz
Cycles:                 351634069514
Instructions retired:   513562913509
Perf event 0:           31412920360
Perf event 1:           972966157
Perf event 2:           1719990
Perf event 3:           14324
Perf event 4:           9535
Perf event 5:           4313396880
Perf event 6:           0
...

Recommend Projects