MétaCan
Menu
Back to cohort

Auto-scaling Compute and Network Resources in a Data-center

2020· article· en· W3103038454 on OpenAlexaff
Anshuman Biswas, Biswajit Nandy, Shikharesh Majumdar, Ali El-Haraki

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsTelus (Canada)Carleton University
Fundersnot available
KeywordsProvisioningCloud computingComputer scienceData centerEnterprise private networkScheduling (production processes)Distributed computingScalingResource allocationProfit (economics)Wide area networkPrivate networkBandwidth (computing)Computer networkOperating systemOperations management

Abstract

fetched live from OpenAlex

This paper focusses on auto-scaling network and compute resources using an intermediary enterprise that uses resources from a public cloud to provide a virtual private cloud to a single client enterprise. The primary goal of the auto-scaling technique is to achieve a profit for the intermediary enterprise while satisfying service level agreements associated with client requests as well as maintaining the desired grade of service for the client enterprise. A secondary goal is to minimize the east-west traffic in the Data Center by reducing the number of network links utilized. Network bandwidth and compute resources are reserved to service the requests from a broker. This paper presents an autoscaling algorithm and includes a discussion of system design. A simulation-based performance analysis is presented to demonstrate the effectiveness of the proposed technique. auto-scaling, resource allocation, dynamic resource provisioning, scheduling with SLAs, resource management on clouds.

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.001
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.003
Threshold uncertainty score0.007

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.034
GPT teacher head0.241
Teacher spread0.207 · 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
Published2020
Admission routes1
Has abstractyes

Explore more

Same topicCloud Computing and Resource ManagementFrench-language works237,207