[DRAFT] Improve the sampling of CodeCarbon
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 323
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Description
Is your feature request related to a problem? Please describe.
At least two other tools has been created because CodeCarbon does not have a sub-second sampling rate:
- Alumet : https://alumet-dev.github.io/user-book/
- WattAMeter : https://github.com/NatLabRockies/WattAMeter
Describe the solution you'd like
Look at these tools and compare them to CodeCarbon to find IF we could improve CodeCarbon to address these concern.
Describe alternatives you've considered
Maybe we don't have to and these tools could co-exist.
Additional context
See https://github.com/mlco2/codecarbon/issues/833#issuecomment-2854222426 from WattAMeter maintainer. And https://github.com/openjournals/joss-reviews/issues/10750#issuecomment-5104399946
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 by comparing CodeCarbon with Alumet and WattAMeter, the tools named in the issue, to assess the current sampling approach. Done means a documented feasibility result and concrete scope for sub-second sampling, or a clear conclusion that the tools should coexist; no files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100