MétaCan
Menu
Back to cohort

Cloud Workload Characterization and Profiling for Resource Allocation

2019· article· en· W3015884705 on OpenAlexaff
Naghmeh Dezhabad, Sudhakar Ganti, Gholamali C. Shoja

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsCloud computingComputer scienceProfiling (computer programming)WorkloadScheduling (production processes)RevenueResource allocationCloud service providerCluster analysisService providerDistributed computingService (business)Computer networkCloud computing securityOperations managementBusinessArtificial intelligenceOperating system

Abstract

fetched live from OpenAlex

Cloud providers aim to efficiently deliver diverse services on demand to users. Recently, they coined the idea of an auction-based market for their resources with the goal of increasing the total revenues. To address the challenge of scheduling and pricing, we build usage profiles for cloud workloads and predict future demands. In this paper, we first present a new methodology to categorize workloads according to their resource usage. We employ a modified hierarchical clustering algorithm that gives us three demand profiles for batch jobs designated as low, medium and high. After that, we extract the number of arrival requests per time for each group. The methodology presented here provides insights to cloud service providers in optimizing resource allocation and improving profits.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.004
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.003
Threshold uncertainty score0.005

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.004
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0030.002
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.001

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.011
GPT teacher head0.219
Teacher spread0.208 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations15
Published2019
Admission routes1
Has abstractyes

Explore more

Same topicCloud Computing and Resource ManagementFrench-language works237,207