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

DRAM consumption output #13

Closed
hassenebyy opened this issue Jul 6, 2021 · 3 comments · Fixed by #20
Closed

DRAM consumption output #13

hassenebyy opened this issue Jul 6, 2021 · 3 comments · Fixed by #20

Comments

@hassenebyy
Copy link

Hi everyone,

I've noticed that the DRAM output is expressed in seconds.
"dram (Optional[List[float]]) – list of the RAM energy consumption -expressed in seconds- (one value for each socket) if None, no RAM energy consumption was recorded."

Can you explain why the energy consumption is not expressed in micro-Joules ?
Otherwise, how can I obtain the equivalence in Joules ?

Thank you,
Best regards.

@av1m
Copy link

av1m commented Aug 12, 2022

I take advantage of this issue to add that the return in seconds seems strange to me.
Indeed, I get results such as [9643.0], [12817.0] for a code that runs in 0.4 seconds

Here is the code

import pyRAPL
pyRAPL.setup()

baz = pyRAPL.Measurement("baz")
baz.begin()
list(range(10000))
baz.end()
print(baz.result.dram)
# [12024.0]

@smenard
Copy link

smenard commented Nov 8, 2022

In the class DramAPI, the file read is energy_uj same name as the one in PkgAPI, guessing that it means energy in micro joule.

@Andlexex
Copy link

Andlexex commented Sep 23, 2023

I would also say, that there is an error in the documentation. The average power that 8gb of RAM require is approx 3W (as a rule of thumb). I ran pyRAPL on just my system for 10 minutes and recorded the energy usage per second into a file.

The results show, that my RAM (of which 0.96GB were allocated at that time) would consume 2063.622961J which corresponds to a power demand of approx 3.439371W.
This would somewhat approve the assumption of the output being displayed in micro Joules for the RAM as well.

iivanoo added a commit to iivanoo/pyRAPL that referenced this issue Nov 7, 2023
The documentation about the unit of measure of DRAM results was telling that those were reported in seconds, whereas they should be in micro-Joules.

This PR fixes powerapi-ng#13
@rouvoy rouvoy closed this as completed in #20 Nov 7, 2023
rouvoy added a commit that referenced this issue Nov 7, 2023
Fix documentation about the DRAM results. Fixes issue #13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants