-
Notifications
You must be signed in to change notification settings - Fork 214
feat: allow setting energy threshold for terminated workload tracking #2209
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
feat: allow setting energy threshold for terminated workload tracking #2209
Conversation
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## reboot #2209 +/- ##
==========================================
- Coverage 92.40% 92.27% -0.13%
==========================================
Files 39 39
Lines 4159 4142 -17
==========================================
- Hits 3843 3822 -21
- Misses 253 257 +4
Partials 63 63 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Add minimum energy threshold filtering for terminated workloads to improve tracking of workloads that are meaningful to the user. The terminated resource tracker now filters out low-energy workloads, keeping only those that consumed significant energy. Side-effect: This reduces memory usage while maintaining tracking of relevant terminated resources. Changes: - Add minTerminatedEnergyThreshold config option (default: 10 joules) - Modify TerminatedResourceTracker with energy-based filtering - Update configuration files for dev and k8s environments Config example: ```yaml monitor: minTerminatedEnergyThreshold: 10 # joules ``` Signed-off-by: Sunil Thaha <sthaha@redhat.com>
4276df0
to
508b726
Compare
|
|
… tracking Signed-off-by: Sunil Thaha <sthaha@redhat.com>
9df2a36
to
700ea62
Compare
|
f7243fd
into
sustainable-computing-io:reboot
Add minimum energy threshold filtering for terminated workloads to improve tracking of workloads that are meaningful to the user. The terminated resource tracker now filters out low-energy workloads, keeping only those that consumed significant energy.
Side-effect: This reduces memory usage while maintaining tracking of relevant terminated resources.
Changes:
Config example: