MétaCan
Menu
Back to cohort
Record W2133099771 · doi:10.1109/pccc.2011.6108101

VM clock synchronization measurements

2011· article· en· W2133099771 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicNetwork Time Synchronization Technologies
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsDaemonComputer scienceVirtualizationClock synchronizationVirtual machineSynchronization (alternating current)ServerCloud computingOperating systemEmbedded systemReal-time computingComputer network

Abstract

fetched live from OpenAlex

A modern twist to clock synchronization is the push towards server virtualization and cloud computing. Distributed applications now often run on geographically-distributed, virtualized servers that are isolated from the underlying hardware. Despite the fact that most applications run well in an abstracted environment without direct hardware access, tight real-time synchronized clocks are still necessary. We performed a set of experiments to quantify the additional clock error when running the NTP daemon inside a Virtual Machine. We found that the delay asymmetry is relatively small when running in a non-virtualized environment, but quite significant in a virtualized environment.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.790
Threshold uncertainty score0.733

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

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.063
GPT teacher head0.223
Teacher spread0.160 · 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