Repository navigation
fix: bound DTLS handshake maintenance - #95
Merged
Merged
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
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.
Stop scanning all 65,536 DTLS capacity slots after every completion batch. Check handshake retransmissions at a 50ms cadence and traverse the existing live-session chain, capturing successors before timeout release. No public API, crypto, capacity or socket tuning changes.
Adds regression coverage for timeout removal, slot reuse, cadence, uncached/established sessions and retransmission backoff. Debug and ReleaseSafe: 183/183 tests pass. Debug and ReleaseFast artifacts build.
60 matched DTLS benchmark runs: aggregate mean throughput +0.6% with one worker and +12.1% with four workers (individual four-worker cases +7.4–15.1%). A 36-run plain-CON control is approximately unchanged. Profiling removes the original 70.2% capacity-scan hotspot and roughly halves sampled user CPU; this fix does not claim a 2x throughput improvement.
Reproduction, limitations and raw measurements are in docs/DTLS_MAINTENANCE.md and its linked JSON datasets.