Update sink on change #1

Closed
opened 2026-06-30 22:34:25 +00:00 by alexandradeas · 0 comments

Currently the sink is set once, if this changes at runtime the entire application needs to be restarted. Instead we should implement a way to update the sink at runtime if a different sink becomes the running sink.

Simple implementation would be to just poll in a subprocess and send a message to the sampler to create a new recorder, complexity comes with how to handover between the recorders. Stopping then starting again would be an option, otherwise interpolate between the last non-zero value and the new recorder's first most recent non-zero value.

Consideration should be taken to ensure resources from the previous recorder are cleaned up so that memory isn't leaked

Currently the sink is set once, if this changes at runtime the entire application needs to be restarted. Instead we should implement a way to update the sink at runtime if a different sink becomes the running sink. Simple implementation would be to just poll in a subprocess and send a message to the sampler to create a new recorder, complexity comes with how to handover between the recorders. Stopping then starting again would be an option, otherwise interpolate between the last non-zero value and the new recorder's first most recent non-zero value. Consideration should be taken to ensure resources from the previous recorder are cleaned up so that memory isn't leaked
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alexandradeas/vibez#1
No description provided.