feat(server): add adaptive tiered message queues for slow clients #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement graceful degradation for slow WebSocket clients by splitting the single message queue into 5 tiered queues based on message frequency: - Tier 1: 5ms intervals (~400 msgs/sec) - Tier 2: 10ms intervals (~200 msgs/sec) - Tier 3: 20ms intervals (~100 msgs/sec) - Tier 4: 50ms intervals (~40 msgs/sec) - Tier 5: 100ms+ intervals + config (~36 msgs/sec) Key changes: - New clients start at tier 3 (20ms) and adapt based on performance - Server tracks drop/delivered ratio per consumer over 5-second windows - Clients upgrade to faster tiers when drops < 2%, degrade when > 10% - Tier 5 is guaranteed minimum - never unsubscribed - Server sends "resolution" message when tier changes - Client disables unavailable interval options in dropdown - Slow consumers are skipped (not blocked) in produce() Removes: - Old single mq_msg_ws queue (replaced by 5 tiered queues) - Stale consumer tracking (replaced by adaptive tiers) - Gap warning UI (replaced by resolution indicator) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
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.
Implement graceful degradation for slow WebSocket clients by splitting the single message queue into 5 tiered queues based on message frequency:
Key changes:
Removes:
🤖 Generated with Claude Code