agnos.is Forums

Unless you know what it is and have REALLY strong feelings about that, nope. You wouldn't be here asking otherwise. You're fine.

Just don't use NFS for large files. It's not good for that.

Problem solved then. You know where the bottleneck is.

Try a test download without NFS and see what happens.

Bad RAM wouldn't present like this. You'd more than likely never get past boot with a DDR5 board having caught it with POST tests, or you'd have thrown a kernel exception by now.

I saw you mentioned that a new LXC container didn't have the traffic problem, so this is definitely something with config somehow.

You have more than enough cores for each then. Probably too many. As a test, try the qbit or jellyfin one in host mode and see if the network performance changes. I'd start going down the rabbit hole of tuning bridged mode network in LXC, or just keep them on host mode.

Are all your containers running in bridged mode or host mode?

You need to remove a bunch of variables here to even start getting down to what may be the issue, but I'm guessing it's just the networking.

• did you run speed tests over protonvpn and is this a paid plan?
• have you tested what your Ubuntu download speed is without VPN or gluetun in the way?
• have you looked at the peer and tracker info to see what's going on there?
• have you tried another torrent client to rule out config issues with qbittorrent?