Very slow speed with wireguard over vless

[Epenko1337]

Server speedtest.net result
Client speedtest.net result with wireguard over vless
Client speedtest.net result with just vless proxy

Client configuration for wireguard over vless:

{
    "log": {
        "loglevel": "debug"
    },
    "inbounds": [
        {
            "tag":"wireguard",
            "port": 51820,
            "protocol":"dokodemo-door",
            "settings":{
                "address":"127.0.0.1",
                "port":51820,
                "network":"udp"
            }
        }
    ],
    "outbounds": [
        {
            "protocol": "vless",
            "settings": {
                "vnext": [
                    {
                        "address": "...",
                        "port": 443,
                        "users": [
                            {
                                "id": "...",
                                "encryption": "none",
                                "flow": ""
                            }
                        ]
                    }
                ]
            },
            "streamSettings": {
                "network": "tcp",
                "security": "reality",
                "realitySettings": {
                    "show": false,
                    "fingerprint": "chrome",
                    "serverName": "...",
                    "publicKey": "...",
                    "shortId": "...", 
                    "spiderX": ""
                }
            },
            "tag": "proxy"
        }
    ]
}

Server configuration:

{
    "log": {
        "loglevel": "warning"
    },
    "inbounds": [
        {
            "listen": "0.0.0.0",
            "port": 443,
            "protocol": "vless",
            "settings": {
                "clients": [...],
                "decryption": "none"
            },
            "streamSettings": {
                "network": "tcp",
                "security": "reality",
                "realitySettings": {
                    "show": false,
                    "dest": "...",
                    "xver": 0,
                    "serverNames": [ 
                        "..."
                    ],
                    "privateKey": "...",
                    "shortIds": [...]
                }
            }
        }
    ],
    "outbounds": [
        {
            "protocol": "freedom",
            "tag": "direct"
        }
    ]
}

Wireguard MTU is 1300. What could be wrong? Is it that much cpu expensive operation to route from xray to wg tunnel?

[devopg]

"protocol":"dokodemo-door",
And where does WireGuard fit into all of this?
I don't quite understand your final configuration. If you are using x3-ui, it would be better if you show screenshots.

[Temtaime]

You can find the configuration here : https://computerscot.github.io/wireguard-over-xray.html

[LittleNewton]

Summary

I had the same problem today.

WireGuard Direct speed test: 150Mbps
WireGuard over VLESS speed test: 30Mbps

Vless performs well with anti-censorship but the overhead was unacceptable. Some comparisons have been made with some on/off components. My proxy server has only one AMD EPYC Gen3 Milan CPU but no CPU peak was observed during WireGuard over Vless testing.

iperf3 SpeedTest results

# iperf3: WireGuard Direct
iperf3 -c 10.2.2.10 -P 1 -R
Connecting to host 10.2.2.10, port 5201
Reverse mode, remote host 10.2.2.10 is sending
[  5] local 10.100.5.2 port 57118 connected to 10.2.2.10 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  1.51 MBytes  12.7 Mbits/sec
[  5]   1.00-2.00   sec  18.0 MBytes   151 Mbits/sec
[  5]   2.00-3.00   sec  19.0 MBytes   159 Mbits/sec
[  5]   3.00-4.00   sec  19.1 MBytes   160 Mbits/sec
[  5]   4.00-5.00   sec  19.1 MBytes   160 Mbits/sec
[  5]   5.00-6.00   sec  19.2 MBytes   161 Mbits/sec
[  5]   6.00-7.00   sec  19.0 MBytes   160 Mbits/sec
[  5]   7.00-8.00   sec  19.0 MBytes   160 Mbits/sec
[  5]   8.00-9.00   sec  19.1 MBytes   160 Mbits/sec
[  5]   9.00-10.00  sec  19.2 MBytes   161 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.14  sec   176 MBytes   146 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   172 MBytes   144 Mbits/sec                  receiver

iperf Done.

# iperf3: WireGuard over vless speed test:
iperf3 -c 10.2.2.10 -P 1 -R
Connecting to host 10.2.2.10, port 5201
Reverse mode, remote host 10.2.2.10 is sending
[  5] local 10.100.5.2 port 52754 connected to 10.2.2.10 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  2.19 MBytes  18.4 Mbits/sec
[  5]   1.00-2.00   sec  5.48 MBytes  45.9 Mbits/sec
[  5]   2.00-3.00   sec  4.02 MBytes  33.7 Mbits/sec
[  5]   3.00-4.00   sec  3.69 MBytes  31.0 Mbits/sec
[  5]   4.00-5.00   sec  3.51 MBytes  29.4 Mbits/sec
[  5]   5.00-6.00   sec  2.99 MBytes  25.1 Mbits/sec
[  5]   6.00-7.00   sec  3.06 MBytes  25.7 Mbits/sec
[  5]   7.00-8.00   sec  3.36 MBytes  28.2 Mbits/sec
[  5]   8.00-9.00   sec  3.18 MBytes  26.7 Mbits/sec
[  5]   9.00-10.00  sec  3.44 MBytes  28.9 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.13  sec  37.8 MBytes  31.2 Mbits/sec   36             sender
[  5]   0.00-10.00  sec  34.9 MBytes  29.3 Mbits/sec                  receiver

iperf Done.

[Temtaime]

Same here. At least 3x slower with vless layer. 100% cpu usage

[abishai]

I have the same issue, something in Wireguard doesn't play nice when being tunneled through vless (VPN in VPN).
I checked 2 setups on the same servers
client -> wireguard inbound -> vless -> freedom works very good, I see almost no slowdown, so I can assume my vless setup is good.
client -> dokodemo inbound -> vless ( -> wireguard on the same server) -> freedom is critically slow.
Both setups uses MTU 1300

I'd rather stick to second setup, because it tunnels ICMP, but only if speed can be fixed somehow