MétaCan
Menu
Back to cohort
Record W2242441826

Analyzing auto-scaling issues in cloud environments

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

VenueComputer Science and Software Engineering · 2014
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsConcordia University
Fundersnot available
KeywordsCloud computingProvisioningComputer scienceScalingData scienceSoftwareOpen researchUtility computingDistributed computingData miningCloud computing securityWorld Wide Web
DOInot available

Abstract

fetched live from OpenAlex

Cloud computing is becoming increasingly widespread and sophisticated. A key feature of cloud computing is elasticity, which allows the provisioning and de-provisioning of computing resources on demand, via auto-scaling. Auto-scaling techniques are diverse, and involve various components at the infrastructure, platform and software levels. Auto-scaling also overlaps with other quality attributes, thereby contributing to service level agreements, and often applies modeling and control techniques to make the auto-scaling process adaptive. A study of auto-scaling architectures, existing techniques and open issues provides a comprehensive understanding to identify future research solutions. In this paper, we present a survey that explores definitions of related concepts of auto-scaling and a taxonomy of auto-scaling techniques. Based on the survey results, we then outline open issues and future research directions for this important subject in cloud computing.

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.002
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.577
Threshold uncertainty score0.657

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
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.006
GPT teacher head0.199
Teacher spread0.193 · 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