MétaCan
Menu
Back to cohort

An Optimum Decision Making Framework for Allocating Spot Instances to Execute Batch Workload in Cloud

2021· article· en· W4200416801 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
KeywordsComputer scienceWorkloadCloud computingFlexibility (engineering)Distributed computingHot spot (computer programming)Window (computing)Job schedulerQuality of serviceCore (optical fiber)Batch processingService (business)Set (abstract data type)Real-time computingMathematical optimizationOperating systemComputer network

Abstract

fetched live from OpenAlex

Among all available cloud-based solutions, spot instances are ideal for batch job execution with flexible completion times and failure tolerance. The combination of spot instance sizes and prices provides flexibility to execute jobs satisfactorily with regards to their computational requirements. However, the demand for each type of batch instance fluctuates over time and it raises some challenges to provide adequate instances to match the workload demand. This makes it necessary to have a mechanism to dynamically adjust the number of instances and assign them to the incoming jobs.In this paper, we propose an optimization-based solution to allocate spot resources for executing arriving batch jobs in the cloud platforms over time. This method manages the trade-off between the cost of renting spot instances and the user-centric quality of service in terms of job waiting time. Given a set of jobs and spot instances of various types, our algorithm selects the best combination of instances in each analysis window. In addition, the method takes into account the job arrival prediction and characteristics of input jobs to adapt the algorithm.

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.003
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation 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.007
Threshold uncertainty score0.014

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.003
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0020.001
Open science0.0020.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0030.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.020
GPT teacher head0.309
Teacher spread0.290 · 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 designSimulation or modeling
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

Citations0
Published2021
Admission routes1
Has abstractyes

Explore more

Same topicCloud Computing and Resource ManagementFrench-language works237,207