You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compare increase in node-exporter-rapl vs kepler_node_package vs kepler_vm_package
Note that the
green is rate(node_rapl_package_joules_total{job="metal-node-exporter"}[${rate}s])
red is sum(rate(kepler_node_package_joules_total{job="metal"}[${rate}s]))
blue is sum(rate(kepler_vm_package_joules_total{job="metal"}[${rate}s]))
Blue (which is fraction of the total power) is reported way higher than the increase in kepler-node-package watts
In the above example, the increase in watts reported by kepler_node_package is as below
sthaha
changed the title
With EXCLUDE_SWAPPER_PROCESS enabled, kepler reports VM power more than the Total node Power
With EXCLUDE_SWAPPER_PROCESS enabled, kepler reports VM power more than actually consumed by VM
Nov 5, 2024
Setup
Deploy latest kepler with
EXCLUDE_SWAPPER_PROCESS
set to true on a baremetalTest
Note that the
rate(node_rapl_package_joules_total{job="metal-node-exporter"}[${rate}s])
sum(rate(kepler_node_package_joules_total{job="metal"}[${rate}s]))
sum(rate(kepler_vm_package_joules_total{job="metal"}[${rate}s]))
Blue (which is fraction of the total power) is reported way higher than the increase in kepler-node-package watts
In the above example, the increase in watts reported by kepler_node_package is as below
It raise from 18.0 to 29.2 =~ 12 W
While kepler_vm_package watts is as follows
It raises from 0.9 to a max of 26.9 W
Additionally, `
abs(
sum(rate(kepler_process_package_joules_total{job="metal"}[20s])) -
sum(rate(kepler_node_package_joules_total{job="metal"}[20s]))
)
The text was updated successfully, but these errors were encountered: