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

Is Ram emissions correct? #629

Open
kordou opened this issue Aug 5, 2024 · 1 comment
Open

Is Ram emissions correct? #629

kordou opened this issue Aug 5, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@kordou
Copy link

kordou commented Aug 5, 2024

  • CodeCarbon version: 2.5.0
  • Python version: 3.10
  • Operating System: LInux

Description

I am running a set of codes on the RunPod server that provides, for example, an Nvidia A100 80GB with a maximum RAM memory allowance of 100 GB. In the results, I see that the ram_total_size is 1 TB, and the energy and emissions show that the RAM has a much greater impact than the GPU, which is not normal as other researchers have found that the GPU has the main consumption. For example, I see GPU power: 102 W and RAM power: 378 W.

I ran the same codes on a Google Colab server with an A100 40GB this time and got GPU power: 50 W and RAM power: 31 W.

So my question is: Can CodeCarbon not be used in shared machines? Or is there something else we need to do in order to have proper emissions?

It took me two months of work to notice this, unfortunately...

Thank you

@benoit-cty
Copy link
Contributor

Sorry about that, could you try with tracking_mode='process' ?

We support Slurm for shared machine, but if you know how to do it for RunPod, we will be happy to add it :

def _read_slurm_scontrol(self):

@inimaz inimaz added the enhancement New feature or request label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants