The idea behind Mux is straightforward: instead of opening a new TCP connection per request, several streams share one connection that is already established, which removes the repeated handshake cost. concurrency caps how many streams ride on one connection; clients usually default it to 8.

When it helps

A modern web page fires dozens or hundreds of requests, each needing a TCP three-way handshake plus a TLS handshake. On a high-latency route that overhead adds up, and Mux visibly cuts page load waiting time. Many small requests is where Mux shines.

SponsoredWhere does the subscription link come from?Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click.Get high-speed nodes

When it makes things slower

All sub-streams share one TCP connection's congestion window, and its retransmissions too. Downloading a large file or watching 4K video, a single stream can saturate that connection while everything else queues behind it, and one packet loss stalls every sub-stream at once. For single-stream bulk traffic, turning Mux off is usually faster.

Three cases where it should stay off

  • With XTLS Vision. Vision gets its advantage from handling the raw TLS stream directly; Mux wraps the traffic in another layer and the optimisation disappears. The upstream guidance is to disable it.
  • When the server does not support it. Mismatched settings cause failed or constantly dropping connections, so if a provider does not say it supports Mux, leave it off.
  • In a chained proxy setup. Enabling Mux on both hops compounds the queueing effect.

How to decide

Do not agonise over the theory — measure it twice. Test page loading and a large download on the same node with the switch in each position, using the methods in latency and speed testing. Mostly browsing? Keep it. Mostly downloading or streaming? Turn it off.