MétaCan
Menu
Back to cohort
Record W4401211238 · doi:10.1109/tnsm.2024.3437165

A Survey on Replica Transfer Optimization Schemes in Geographically Distributed Data Centers

2024· article· en· W4401211238 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

VenueIEEE Transactions on Network and Service Management · 2024
Typearticle
Languageen
FieldComputer Science
TopicDistributed and Parallel Computing Systems
Canadian institutionsCarleton University
Fundersnot available
KeywordsComputer scienceReplicaTransfer (computing)Distributed databaseDistributed computingData centerComputer networkParallel computing

Abstract

fetched live from OpenAlex

Data centers have undergone significant expansions in recent years, as cloud service providers seek to improve the quality of service and reduce operational costs. Cloud providers are investing heavily in inter-data center wide-area networks, which help to transport traffic between geographically distributed data centers. However, efficient workload management in complex large-scale networks with a dynamic environment is challenging. In this regard, researchers have developed various solutions to address different challenges for data transfer in inter-data center networks. In this paper, we present a comprehensive review of recent strategies and optimization schemes proposed in the literature to optimize data transfer in geographically distributed data centers. This review paper examines the challenges of data delivery and classifies recent existing solutions for addressing the issues based on communication patterns, objectives, proposed communication frameworks, and evaluation methods. In this study, we provide valuable insights into the current challenges and identify several promising research directions that require significant research endeavors in the future. The findings of this study are useful for researchers and practitioners interested in optimizing data transfer in inter-data center networks.

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: Methods · Consensus signal: none
Teacher disagreement score0.991
Threshold uncertainty score0.804

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.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.028
GPT teacher head0.250
Teacher spread0.222 · 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