MétaCan
Menu
Back to cohort
Record W1880476883 · doi:10.1109/wordsf.1999.842329

Batching earliest deadline first scheduling

2003· article· en· W1880476883 on OpenAlexaff
Maryam Moghaddas, Babak Hamidzadeh

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicReal-Time Systems Scheduling
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsComputer scienceScheduling (production processes)Dynamic priority schedulingEarliest deadline first schedulingDistributed computingFixed-priority pre-emptive schedulingDeadline-monotonic schedulingPrioritizationFair-share schedulingRate-monotonic schedulingProcessor schedulingReal-time computingMathematical optimizationQuality of serviceComputer networkResource (disambiguation)

Abstract

fetched live from OpenAlex

Investigates the trade-off in the dynamic scheduling of real-time tasks, between the frequency at which the scheduling algorithm is invoked, the size of the task set to which the scheduling (prioritization) policy is applied at every invocation, and the quality of the resulting schedules in terms of deadline compliance. We identify two classes of algorithms, one of which forms a batch of arrived tasks and which schedules and executes all tasks in a batch before considering other tasks that arrive in the meantime. The other class accounts for and schedules arrived tasks more frequently and applies the scheduling policy to all available tasks. We compare the performance of a batching and a non-batching technique, both of which apply an earliest-deadline-first (EDF) policy to prioritize tasks. An experimental evaluation of the proposed algorithms shows that our batching algorithms outperform their non-batching counterparts under tighter time constraints.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.006
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.005
Threshold uncertainty score0.016

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.006
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0010.002
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0030.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.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.014
GPT teacher head0.227
Teacher spread0.213 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations4
Published2003
Admission routes1
Has abstractyes

Explore more

Same topicReal-Time Systems SchedulingFrench-language works237,207