MétaCan
Menu
Back to cohort
Record W2112363973 · doi:10.1109/icdcs.1995.500051

Write caching in distributed file systems

2002· article· en· W2112363973 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Data Storage Technologies
Canadian institutionsUniversity of Saskatchewan
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceFalse sharingLocalityCacheServerOperating systemFile serverLocality of referenceDisk bufferWorking setSet (abstract data type)Computer networkCPU cacheDistributed computingCache algorithms

Abstract

fetched live from OpenAlex

Disk caches are employed in distributed file systems to avoid network accesses at clients and to compensate for the speed differential between main memory and disk at file servers. Because of concerns about volatility, however, write requests have typically not benefitted from the presence of caches. Instead, they have been processed with some sort of write-through or periodic write-back approach to ensure the integrity of the stored data. The introduction of reasonably priced non-volatile (NV) memories has prompted interest in the use of such memory for write caching, at the server and/or at the client. This paper describes an investigation through trace-driven simulation experiments of several approaches to write caching in distributed systems, with both volatile and non-volatile caches. The results support the findings of earlier work that suggests important differences between caching in the traditional single-level caching environment and caching in a two-level caching environment. While policies focusing on temporal locality perform well for a single-level caching system, or at the client of a two-level caching system, they may not be suitable for use at the server in a two-level caching system. This is because locality characteristics in the reference stream seen at the server in a two-level caching system may be destroyed by caching at the client with a NV write cache large enough to hold the client's working set of dirty blocks. Policies focusing on amortizing the cost of a disk seek operation over multiple write-back operations perform better at the server of a two-level caching system.

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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.934
Threshold uncertainty score0.284

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.000
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.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.023
GPT teacher head0.227
Teacher spread0.205 · 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

Quick stats

Citations10
Published2002
Admission routes2
Has abstractyes

Explore more

Same topicAdvanced Data Storage TechnologiesFrench-language works237,207