MétaCan
Menu
Back to cohort
Record W2025213465 · doi:10.1515/itit-2014-1016

A framework for autonomic workload management in DBMSs

2014· article· en· W2025213465 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

Venueit - Information Technology · 2014
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsIBM (Canada)Queen's University
Fundersnot available
KeywordsWorkloadComputer scienceOnline transaction processingIBMTransaction processingDatabaseDistributed computingOperating systemDatabase transaction

Abstract

fetched live from OpenAlex

Abstract In today's database server environments, multiple types of workloads can be present in a system simultaneously. Workload types may include on-line transaction processing and business intelligence. Workloads may also have different levels of business importance and distinct performance objectives, which are typically derived from service level agreements. An autonomic workload management system for database management systems (DBMSs) dynamically monitors and controls the flow of the workloads to help DBMSs achieve the desired performance objectives. In this paper, we present a framework and a prototype implementation for autonomic workload management in DBMSs. The framework and the prototype provide the ability to achieve performance objectives of workloads with diverse characteristics, different levels of business importance and varying resource demands while protecting DBMSs against performance failure. The prototype system is implemented on top of IBM ® DB2 ® Workload Manager. Initial experiments using the prototype system are presented to demonstrate the effectiveness of the framework.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.686
Threshold uncertainty score0.426

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.008
GPT teacher head0.240
Teacher spread0.231 · 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