Clarification about Metrics like CPU Power and CPU Energy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 323
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Description
- 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CodeCarbon output documentation, especially the HTTP output section, and investigate how CPU, GPU, memory, and Emissions values are scoped. Done means the documentation clearly states whether values represent the tracked process, experiment, or complete node, including the Kubernetes context described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100