Optimize hot paths: DNS resolution, UDP cleanup, buffer management, and HTTP2 allocations #468
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.
Identified and fixed performance bottlenecks in network I/O hot paths causing unnecessary allocations, redundant iterations, and lock contention.
DNS Resolver (
protocols/dns/resolver.rs)partition()insort_socket_addrsBefore:
After:
UDP Server (
protocols/udp/server.rs)iter()+clear()withdrain()in dead key cleanupWebsocket Transport (
tunnel/transport/websocket.rs)reserve()adds to capacity, not sets itreserve(capacity + capacity/4)→ actual growth ~56%reserve(capacity/4)→ correct 25% growthHTTP2 Transport (
tunnel/transport/http2.rs)LazyLock<Arc<Notify>>instead of allocating per tunnelOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.