MétaCan
Menu
Back to cohort
Record W2085367298 · doi:10.5555/2821357.2821380

Adaptive management of energy consumption using adaptive runtime models

2015· article· en· W2085367298 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSoftware Engineering for Adaptive and Self-Managing Systems · 2015
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsComputer scienceEnergy consumptionFeature extractionData miningScheduling (production processes)Classifier (UML)Energy managementScheduleArtificial intelligenceData centerAdaptive controlMachine learningReal-time computingEnergy (signal processing)Control (management)Engineering

Abstract

fetched live from OpenAlex

A promising avenue to control energy-related costs in enterprise data centers is to investigate power-aware resource management strategies. In this study we investigate techniques to schedule resources adaptively with the sole aim of reducing power consumption. Our approach is based on a characterization of energy usage and resource utilization patterns obtained by monitoring energy consumption in an enterprise data center. We propose an adaptive feature extraction method to classify resource utilization patterns from energy consumption data. Improved classification results are obtained through signal feature extraction prior to the training stages for cascading classifiers for at least 14 different energy usage patterns. Adaptive feature extraction prior to classifier training improved class identification even further. The identified patterns can now be used as a basis for adaptive resource scheduling within a power-smart data center. The classification method that performed best is part of our proposed energy runtime model and controller which manages and controls the energy consumption in the data center according to usage patterns.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.784
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.036
GPT teacher head0.224
Teacher spread0.188 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it