Heuristic/Configurable Snell v2 Connection Pool Warmup

baldnbrave

It seems like the MaxConnections for the snell TCP pool set in Surge iOS is 8.

In a scene of low concurrency web browsing on a large RTT server, a lower threshold for multiplexing TCP connections will reduce the response time and latency.

Based on my experience, browsing instagram/twitter after opening a high concurrency app (like telegram) will have more chance to reuse the TCP connections than opening them before opening telegram.

Now that Surge has statistics of connection speed and average RTT, would it be possible to make the multiplexing threshold heuristic based on current TCP connections, RTT and connection speed? This will only be a logic for the snell client.

@SurgeTeam

baldnbrave

Some mechanism like TCP congestion control is a possible option. @SurgeTeam

SurgeTeam

Surge Snell client doesn't have a general connection pool design. Surge will check if there is an idle Snell connection existing if a request uses a Snell policy.

If there is no idle connection, a new Snell connection will always be created, without a maximum limitation.

When a Snell connection has finished its request, Surge moves it to the idle connection pool and closes it after about 30s if no new request uses it.

tlhc

maybe the idle time of connection can be set via config file?