MétaCan
Menu
Back to cohort

Adaptive Replica Placement in Hierarchical Data Grids

2010· article· en· W2009544283 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

VenueJournal of Physics Conference Series · 2010
Typearticle
Languageen
FieldComputer Science
TopicDistributed and Parallel Computing Systems
Canadian institutionsUniversity of Manitoba
FundersNatural Sciences and Engineering Research Council of CanadaUniversity of Manitoba
KeywordsComputer scienceReplicaScalabilityDistributed computingData accessData gridLatency (audio)GridReplication (statistics)Fault toleranceBandwidth (computing)Computer networkDatabase

Abstract

fetched live from OpenAlex

Data grids support distributed data-intensive applications that need to access massive (multi-terabyte or larger) datasets stored around the world. Ensuring efficient and fast access to such widely distributed datasets is hindered by the high latencies of wide-area networks. To speed up access, data files can be replicated so users can access nearby copies. Replication also provides high data availability, decreased bandwidth consumption, increased fault tolerance, and improved scalability. Since a grid environment is highly dynamic, resource availability, network latency, and users requests may change frequently. To address these issues a dynamic replica placement strategy that adapts to dynamic behavior in data grids is needed. In this paper, we extend our earlier work on popularity-based replica placement proposing a new adaptive algorithm for use in large-scale hierarchical data grids. Our algorithm dynamically adapts the frequency and degree of replication based on data access arrival rate and available storage capacities. We evaluate our algorithm using OptorSim. Our results show that our algorithm can shorten job execution time greatly and reduce bandwidth consumption compared to its non-adaptive counterpart which outperforms other existing replica placement methods.

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: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.931
Threshold uncertainty score0.438

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0020.001
Research integrity0.0000.001
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.051
GPT teacher head0.284
Teacher spread0.232 · 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