Disk polling: measure owner completion service under concurrent polling

Aperta
  • Qualcosa non va?
#4,177 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
distributed-systems, performance

Direzione di ricerca

Inizia con la configurazione condivisa del benchmark e i criteri di valutazione in #4174, quindi leggi core/shard/src/router.rs, core/shard/src/poll/completion.rs e core/configs/src/server_config/sharding.rs. Riutilizza la cattura dello stage padre ed esegui un breve ramp-up di letture concorrenti, se giustificato. Il lavoro è completato quando sono state registrate le misure richieste relative a carico, ammissione, coda, memoria, avanzamento delle scritture e latenza, con qualsiasi confronto tra policy allineato alle guardrails.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

performance server

Part of #4174, which records the shared benchmark setup and evaluation criteria.

Measure whether admission or owner service limits disk polling under concurrent load. The owner pump services one completion after ordinary work and also has a completion select arm. Capacity is reserved before I/O and held until dequeue or discard.

The limit counts running reads plus queued completions, including reads continuing after requester timeout. It bounds operations, not retained bytes or time spent waiting behind owner work.

An earlier diagnostic used base 0d862e36dcc42fd1fffca2f4504886718bf7757f plus an instrumented port of the archived lane, rather than the current implementation. At capacity 1024:

Observation Without writes With writes
Maximum ordinary inbox occupancy sampled at pump starts 1 2
Maximum candidate reservation occupancy 1 1
Maximum candidate completion queue occupancy 1 1
Rejected candidate reservations 0 0

This separate diagnostic comprised eight captures of 10,000 explicit offset polls, using the shared sequential consumer workload described in #4174. Its report and captures remain archived locally. Pump samples can miss brief peaks; these observations establish neither saturation nor a benefit from greater capacity. Instrumented timings are not a clean performance comparison.

  1. Reuse the parent's stage capture. If owner service appears material or a representative concurrency requirement warrants it, run a short ramp with several simultaneous reads and ordinary work.
  2. Record offered and completed load, active reads, reserved capacity, queue occupancy, admission rejections, retained bytes, write progress and tick delay.
  3. Separate enqueue to owner acceptance from acceptance to caller resumption. Correlate waits with actual owner work and service intervals, sharing timestamps with #4178.
  4. If a specific boundary explains material delay, compare one bounded policy change at matched load. Use completion latency, achieved write throughput and tick latency as guardrails.

Preserve bounded admission, reservation release and history validation on the owner. Larger drains can delay consensus, other replies or shutdown; greater capacity can admit more detached I/O and retain more data. Use the parent's arrival model guidance so a slowing sequential client does not conceal the pressure being studied.

Lingua principale
Rust
Stelle
5.2k
Fork
502
Merge medio
3g 11h
PR unite (30g)
143

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/iggy

Tutte le issue di apache/iggy

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.