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

Two Kepler deployed on same machine report different power usage #1881

Open
vprashar2929 opened this issue Dec 4, 2024 · 1 comment
Open
Labels
kind/bug report bug issue

Comments

@vprashar2929
Copy link
Collaborator

What happened?

When two instance of same Kepler versions are deployed on same BM machine and then stress is applied to the machine both Kepler versions report power values that are different from each other.

Attaching below screenshot for reference:

Screenshot 2024-12-04 at 5 17 59 PM

Screenshot 2024-12-04 at 5 18 14 PM

What did you expect to happen?

Since there are no code changes and both Kepler instances are using the same Kepler version ideally they should report the same power values

How can we reproduce it (as minimally and precisely as possible)?

  1. Deploy two versions of Kepler using dev compose manifests
  2. Compare below Kepler dev vs latest metrics:
sum( rate( kepler_process_package_joules_total{ job="dev", }[20s] ) )
sum( rate( kepler_process_package_joules_total{ job="latest", }[20s] ) )

sum( rate( kepler_process_core_joules_total{ job="dev", }[20s] ) )
sum( rate( kepler_process_core_joules_total{ job="latest", }[20s] ) )

sum( rate( kepler_process_dram_joules_total{ job="dev", }[20s] ) )
sum( rate( kepler_process_dram_joules_total{ job="latest", }[20s] ) )

sum( rate( kepler_process_other_joules_total{ job="dev", }[20s] ) )
sum( rate( kepler_process_other_joules_total{ job="latest", }[20s] ) )

Anything else we need to know?

No response

Kepler image tag

latest

Kubernetes version

$ kubectl version
# paste output here

Cloud provider or bare metal

BM

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Kepler deployment config

For on kubernetes:

$ KEPLER_NAMESPACE=kepler

# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE}
# paste output here

# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE}

For standalone:

put your Kepler command argument here

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

@vprashar2929 vprashar2929 added the kind/bug report bug issue label Dec 4, 2024
@vprashar2929
Copy link
Collaborator Author

cc: @rootfs @KaiyiLiu1234

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug report bug issue
Projects
None yet
Development

No branches or pull requests

1 participant