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

Clarification about Metrics like CPU Power and CPU Energy #679

Open
altruistcoder opened this issue Sep 25, 2024 · 1 comment
Open

Clarification about Metrics like CPU Power and CPU Energy #679

altruistcoder opened this issue Sep 25, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@altruistcoder
Copy link

altruistcoder commented Sep 25, 2024

  • CodeCarbon version: 2.5.0
  • Python version: 3.11.4
  • Operating System: Linux-5.15.0-116-generic-x86_64-with-glibc2.35

Description

Hello,

I recently got introduced to Code Carbon for tracking emissions produced by our machine learning experiments and I am currently exploring the same for our use case.

I am having a bit of unclarity on certain metrics found out by Code Carbon which includes metrics like CPU, GPU & Memory Power and CPU, GPU and Memory Energy, on whether the results for these metrics take into consideration only the process executing the experiment or code carbon tracks the complete node (on which the pod is running inside which the experiment is being run) in the tracking duration and the metric values that come up in the results are for complete node instead of being for the particular machine learning experiment only?

Similarly, the values we get for the Emissions parameter field represent the total emissions produced by the node in the tracking duration or is it the value for that particular machine learning experiment only?

I tried going through the official documentation but couldn't find much information on it:

https://mlco2.github.io/codecarbon/output.html#http-output

So, if anyone could please provide some information on this topic or guide me through the right documentation, then it would be very helpful.

@benoit-cty
Copy link
Contributor

By default it's the complete node.

You have a tracking_mode but to be honest, it works only for RAM right now.

For GPU, you could mask the GPU you doesn't want to track with CUDA_VISIBLE_DEVICES

@benoit-cty benoit-cty added documentation Improvements or additions to documentation question Further information is requested labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants