Address review feedback: Make sweep interval configurable #3
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.
The original PR had a hardcoded 100ms interval for the marker sweep timer. This has been made configurable.
Changes:
sweepIntervalMsoption to plugin constructor (defaults to 100ms)frameDurationMsoption to configure frame timing assumptions (defaults to 200ms)lostThresholddocumentation clarifying it's measured in frames_sweepMarkers()to uselostThreshold * frameDurationMsfor threshold calculationUsage:
Consumers can now tune marker cleanup frequency based on their capture rate and latency requirements.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.