feat(client): implement FastStart for early connection and background resolver discovery - #205
Open
taskkillstar wants to merge 9 commits into
Open
feat(client): implement FastStart for early connection and background resolver discovery#205taskkillstar wants to merge 9 commits into
taskkillstar wants to merge 9 commits into
Conversation
Author
|
Minimizes startup time (no need to scan the entire resolvers list), allows to have several hundreds of resolvers in the list without sacrificing connection time. Requested by FR #179 |
…speed qualification - Add pipelined micro-burst speed prober to detect rate-limiting and burst packet loss - Add candidate ranking score and top-N active pool selection (MAX_ACTIVE_RESOLVERS) - Add initial balancer stat seeding (SeedBurstStats) and set Loss-Then-Latency (6) as default strategy - Add micro-burst qualification on background inactive resolver reactivation - Update client config, sample configs, and all 6 localized READMEs with full documentation
…ection, and enriched reactivation log
…d latency-based demotion/promotion
… resolvers for fast warm-start - Preserved natural input order in LoadClientResolvers without forced sorting - Added managed header block in client_resolvers.txt to persist top-performing resolvers across runs - Added AUTO_SAVE_RANKED_RESOLVERS configuration option (default: true) - Added Balancer.GetRankedEndpoints and Client.SaveRankedResolversToFile - Auto-saves upon initial MTU test completion, pool optimization swaps, and graceful shutdown - Added unit tests for order preservation, atomic file update, and endpoint ranking - Synchronized documentation, CLI parameters, and samples across all README files
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.
Summary
When configured with large resolver lists (e.g. 50–100+ endpoints), the client previously blocked session initialization and local proxy (SOCKS5/DNS) startup until 100% of all resolvers were synchronously probed for MTU.
This PR introduces FastStart:
unResolverHealthLoop\ discovers and reactivates them asynchronously without blocking user traffic.
Key Changes
Verification