mlco2 / mlco2/codecarbon

Tracking temperature of GPU/CPU

Open
#1,008 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
1.9k
Forks
323
Avg merge
1d 12h
Merged PRs (30d)
12

Description

First, thank you for this project! I really love it.

Do you plan to provide a way to track GPU/CPU temperatures?

If not, could you recommend a method to do this? I’ve already found a few possibilities but am open to other ideas. Ideally, it would be great to have the temperature stored in the emissions.csv file—perhaps as the average temperature per device during a training process.

I’m asking because I recently noticed some performance “degradation” during summer and warm spring temperatures. You can see an example in this report:
GPU Efficiency in VLAI Model Training.
(or see the joined picture)

In the section "Evolution of Experiments in Environment A", the charts were generated directly from CodeCarbon data. It’s really interesting, but I’m missing temperature data.

Again, if there is no way or you are not planning to add this possibility, all good. In this case I will find other ways.

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, entry points, or tests. Start by locating the per-device measurement flow and emissions.csv output, then investigate supported CPU/GPU temperature sources and define how an average temperature per device should be represented; done means the scope, platform support, and CSV behavior are specified and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.