Comment on PSA: Flow Control and Port Buffers are key to fix poor uplink speeds
non_burglar@lemmy.world 1 week ago
Wow, you diagnosed buffer bloat and applied the fix to your LAN side? Sooo much work…
The problem is unlikely to have been on the proxmox side. Multiqueue only allows virtio to multithread TCP connections via the host CPU using more than one virtual cpu, but this is essentially like aggregating a network link; it will increase bandwidth, but not throughput. Besides, the actual limit for the proxmox internal bridge and virtio NICs is “whatever the cpu can manage”, which is sometimes over 10Gb. It’s unlikely to be slowing down traffic coming from your vms.
Smash@lemmy.self-hosted.site 1 week ago
Yeah, two whole days of work 😅 The alternative would have been to install a dedicated 1GbE NIC in the servers again. The tunables and proxmox settings probably don’t do anything now but maybe in the future when I finally get FTTH. I read a lot about OPNsense performance optimization and these tweaks shouldn’t hurt anything, so might as well apply them for good measure.
non_burglar@lemmy.world 1 week ago
Well, seems like it was time well spent in any case.
If you have classic upstream buffer bloat, there are a couple of traffic shaping algorithms (cake and fq_codel) that work really well with the majority of competent routers, including opnsense/pfsense.
Traffic shaping is definitely a can of worms, but fun to learn.
Smash@lemmy.self-hosted.site 1 week ago
Yeah… well spent… not that I could just have, you know, used the ISP router and spend my time on other things ^^
I would rather not introduce any more complexity into the routing than needed. I just hope my current setup allows the networking gear to automatically adjust itself for best performance (which it now does).