Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Lock free ringbuffer for alive notifications

Aperta
  • Qualcosa non va?
#855 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
48/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
backend

Direzione di ricerca

Read score/launch_manager/src/daemon/src/alive_monitor/details/ipc/ringbuffer.hpp and the existing score/launch_manager/src/daemon/src/common/concurrency/mpsc_bounded_queue.hpp. Trace the alive checkpoint reporting path and the internal communication usage in supervision_event.hpp; the issue also calls for a reader/writer stress test under thread sanitizer. Done means checkpoint reporting uses a SPSC lock-free ring buffer and internal communication uses the existing queue.

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

Descrizione

performance
What

Context

Applications can send alive notifications to the launch manager for health monitoring.
Each application process gets its own shared memory for this (freedom from interference).
Application process writes checkpoint into the memory, Launch Manager reads checkpoints from the shared memory.
The shared memory contains a ring buffer implementation.

Problem

This ring buffer is currently implemented with a mutex, which performs badly (at least on QNX) due to the kernel calls involved.
Specifically, Launch Manager may check all shared memories every 10ms for content, which requires the expensive mutex locking even if no checkpoints have been reported.

Solution

Change the implementation to a simple lock-free implementation for a single Producer (Application process), single consumer (Launch Manager).
Add a "stress test" with a reader and writer thread that runs under thread sanitizer.

The current ring buffer is also used in another place for communication btw. alive monitor thread and worker threads.
This usage shall be replaced with the existing MPSC queue. This communication is not IPC communication and it was only using the ipc ringbuffer for legacy reasons.
You might want to add the getOverflow() flag to the generic mpsc queue or add a wrapper that supports this.

Acceptance Criteria (DoD)
  • Alive checkpoint reporting uses a SPSC lock free ringbuffer
  • Launch Managers Internal communication migrated to use the existing queue implementation
How

No response

Lingua principale
C++
Stelle
6
Fork
35
Merge medio
2g 6h
PR unite (30g)
92

Preparare l'ambiente

Apri in Codespaces

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

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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 eclipse-score/lifecycle

Tutte le issue di eclipse-score/lifecycle

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.