Repository navigation
feat(benchmarks): report connection port resources - #75
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.
Repeated connection-load runs can fail while allocating a local address before they reach their connection target. Record the ephemeral-port range at startup and capture the first connection error's code, category, established count and port-resource snapshot before cleanup. This keeps setup pressure distinguishable from a stall after all connections are established.
Both native benchmarks share the implementation. macOS queries the default port range; Linux also reads the network namespace's all-process TCP TIME_WAIT count. Unsupported queries and OS errors remain explicit. The tool does not estimate free connection capacity or change system settings or limits.
Validation on macOS arm64 / Boost 1.92 / Release / TLS off, synchronized with accepted #74: nine resource cases and six observer cases passed, together with native argument/self checks, help, a controlled one-connection timeout/cleanup regression, and complete clang-format 18 checks. The standalone module also passed Nimbus and bilingual benchmark-manual checks. Linux/Windows execution remains for hosted acceptance.
This improves diagnostics for the invalid setup trials recorded in #61; it does not repair or close the established-connection TCP stall. Raw measurements and logs remain local.