Skip to content
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

CPU / DRAM Energy Consumption #93

Closed
ib31iat opened this issue Jan 20, 2025 · 2 comments
Closed

CPU / DRAM Energy Consumption #93

ib31iat opened this issue Jan 20, 2025 · 2 comments

Comments

@ib31iat
Copy link

ib31iat commented Jan 20, 2025

Do I see correctly that CarbonTracker only reads the the package RAPL file (/sys/class/powercap/intel-rapl:0/energy_uj) if it is available? On most machines this does not include DRAM energy consumption (see: https://hubblo-org.github.io/scaphandre-documentation/explanations/rapl-domains.html).

Would that mean that CarbonTracker, contrary to what is written in the paper, only consider the Power of the CPU or do I miss something?

@Snailed
Copy link
Collaborator

Snailed commented Feb 5, 2025

Hello @ib31iat, thanks for bringing this to our attention.
It seems to me that you are correct - Carbontracker in its current state only reads package RAPL files /sys/class/powercap/intel-rapl:0/energy_uj whereas DRAM is located in a subdirectory to this (for example /sys/class/powercap/intel-rapl:0/intel-rapl:0:1/energy_uj).

The RAPL zone hierarchy, clarified in this issue on the powercap repository, specifies that the energy_uj for the package zone does not include DRAM even though it is a subdirectory to the package directory. The original authors of carbontracker believed otherwise at the time it seems. Luckily, DRAM does not contribute much to the total energy consumption of a system.

I have made a fix for this - now it should measure both the package and DRAM files. Am testing on different devices now to validate.

@Snailed
Copy link
Collaborator

Snailed commented Feb 6, 2025

This has now been fixed in version v2.1.2. Closing the issue.

@Snailed Snailed closed this as completed Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants