MétaCan
Menu
Back to cohort
Record W2518601541 · doi:10.1109/sai.2016.7556142

An analysis of live migration in openstack using high speed optical network

2016· article· en· W2518601541 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

Venue2016 SAI Computing Conference (SAI) · 2016
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsnot available
Fundersnot available
KeywordsDowntimeLive migrationComputer scienceVirtual machineVirtualizationLatency (audio)Operating systemHost (biology)Computer networkCloud computingTelecommunications

Abstract

fetched live from OpenAlex

Virtualisation technology has become a very common trend in modern datacentres as Virtual Machine (VM) migration brings several benefits like improved performance, high manageability, resource consolidation and fault tolerance. Live Migration (LM) of VMs is used for transferring a working VM from one host to another host of a different physical machine without interfering with the existing VMs. However, little research has been done in considering the real time resource consumption and latency of live VM migration that reduces these benefits to much less than their potential. In this paper, we present an analysis of LM in our unique TransAtlantic high speed optical fibre network connecting Northern Ireland, Dublin and Halifax (Canada). We show that the total migration times as well as total network data transfer for post-copy LM are both dominated by specific VM memory patterns using loaded or unloaded VMs. We also found that the downtime for different VM memory patterns is not extremely varied and no severe effect is experienced over our long distance network.

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.001
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: Empirical
Teacher disagreement score0.354
Threshold uncertainty score0.870

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.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.028
GPT teacher head0.274
Teacher spread0.246 · 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