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

Wrong watt consumptions #241

Closed
CracKOl opened this issue Nov 16, 2022 · 5 comments
Closed

Wrong watt consumptions #241

CracKOl opened this issue Nov 16, 2022 · 5 comments
Labels
bug Something isn't working
Projects

Comments

@CracKOl
Copy link

CracKOl commented Nov 16, 2022

Bug description

First of all, thanks for sharing this tool !

I've deployed the last version on k3S with no pb. Then i have imported the scaphandre dashboard from grafana.com, using its ID : It works fine, i have data displayed but the watt consumption are too low compared to the measure i do with my wattmeter.
I mesure 34w on my device when grafana displays 12 to 15w.

Expected behavior

Calculate the right watt consumption.

Environment

  • Linux distribution 22.04
  • Kernel version 5.15.0-53-generic
  • containerd://1.6.8-k3s1
  • k3s v1.24.7+k3s1

Mini server :
DELL Optiplex
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz

@CracKOl CracKOl added the bug Something isn't working label Nov 16, 2022
@autolyticus
Copy link

The power measurement that RAPL measures (which Scaphandre uses) cannot be equal to the wattmeter readings and it will always be lower.

RAPL estimates CPU and DRAM power consumption using some features and models that are provided on Intel processors.

CPU and DRAM aren't the only power consuming entities on your system. So when you measure the "Socket power" with the Wattmeter, you are also adding the measurement of the

  1. Motherboard
  2. NIC
  3. Cooling (Fans etc)
  4. Peripherals (if any)

image [1]

The important point about using Scaphandre (or any other software meter) is that it gives you a very accurate way to measure the dynamic aspects of power consumption. You can't really control the power consumption of the PCI slots or motherboard. But you can control the power consumption of the CPU and DRAM by optimizing your workloads.

[1] - A.-C. Orgerie, M. D. de Assuncao, and L. Lefevre, “A survey on techniques for improving the energy efficiency of large-scale distributed systems,” ACM Comput. Surv., vol. 46, no. 4, pp. 1–31, Apr. 2014, doi: 10.1145/2532637.

@maethor
Copy link

maethor commented Dec 15, 2022

Hello. We are working on this issue in another project which results will eventually be used by Scaphandre and other monitoring tools : #201 (comment)

A difference of ~20W could be mainly explained by storage devices (~5W per SSD and ~15W per hard drive).

@bpetit bpetit added this to Triage in General Dec 18, 2022
@bpetit bpetit moved this from Triage to To do in General Feb 8, 2023
@bpetit
Copy link
Contributor

bpetit commented May 18, 2023

linking this to #140, #117 and #25

Note that next release (1.0.0) should include an estimation of hard drives consumption as well as RAPL measurements.

@bpetit
Copy link
Contributor

bpetit commented May 25, 2023

link to #116 as well

@bpetit
Copy link
Contributor

bpetit commented Mar 6, 2024

If your machine supports it, you could now (since 1.0.0) leverage the new PSYS based value that should closer to a wattmeter-based metric (see https://hubblo-org.github.io/scaphandre-documentation/explanations/rapl-domains.html for an explanation on PSYS).

As said previously evaluating other components without RAPL is part of the roadmap, see #24 #330 #289 ...

I'll close this issue as this is somehow a description of the purpose of the whole project to get a wider coverage of components.

@bpetit bpetit closed this as completed Mar 6, 2024
General automation moved this from To do to Done Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants