Always send recording_id as part of LogMsg#1778
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our comms were previously somewhat stateful -- we assumed all messages received after a BeginRecording belonged to that recording. However, smart channels (as well as rrd files, web sockets, etc.) allow many sessions, including those with different recording_ids, to become interlaced, introducing ambiguity as to which recording a given message belonged to.
This adds some additional overhead to the LogMsg by sending RecordingId per-message.
Before:
After:
Performance benches seem to be in the noise:
However, this overhead will be substantially mitigated by the new batching logic.
Resolves: #903
Checklist