MétaCan
Menu
Back to cohort
Record W2745255455 · doi:10.1109/tnsm.2017.2738026

Simultaneous Cost and QoS Optimization for Cloud Resource Allocation

2017· article· en· W2745255455 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueIEEE Transactions on Network and Service Management · 2017
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsUniversity of Calgary
FundersNatural Sciences and Engineering Research Council of CanadaAlberta Innovates - Technology Futures
KeywordsCloud computingComputer scienceQuality of serviceSoftware deploymentWorkloadResource allocationDistributed computingService providerComputer networkService (business)Operating system

Abstract

fetched live from OpenAlex

Cloud computing is a new era of computing that offers resources and services for Web applications. Selection of optimal cloud resources is the main goal in cloud resource allocation. Sometimes, customers pay more than required since cloud providers' pricing strategy is designed for the interest of the providers. Nonetheless, cloud customers are interested in selecting cloud resources to meet their quality of service (QoS) requirements. Thus, for the interest of both providers and customers, it is vital to balance the two conflicting objectives of deployment cost and QoS performance. In this paper, we present a cost-effective and runtime friendly algorithm that minimizes the deployment cost while meeting the QoS performance requirements. In other words, the algorithm offers an optimal choice, from customers' point of view, for deploying a Web application in cloud environment. The multi-objective optimization algorithm minimizes cost and maximizes QoS performance simultaneously. The proposed algorithm is verified by a series of experiments on different workload scenarios deployed in two distinct cloud providers. The results show that the proposed algorithm finds the optimal combination of cloud resources that provides a balanced trade-off between deployment cost and QoS performance in relatively low runtime.

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 categoriesScience and technology studies
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.941
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0020.000
Scholarly communication0.0010.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.014
GPT teacher head0.234
Teacher spread0.220 · 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