I recently started 4 new nodes using my TrueNAS. The buffer related message looks like this:
INFO failed to sufficiently increase send buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
According to the github link this is about high-bandwidth connections. Running a number of storj nodes at home sharing a 100 mbit internet connection is obviously not a high-bandwidth thing.
I am knowing how to set the buffer size for linux but TrueNAS doesn’t want users to change such things directly. It is possible but not recommended. So I would prefer to ignore this message if the possible gain is negligible.
Network card is 10 GBe Mellanox Connect-X 3, so not a consumer card. But as far as I know the buffer we are talking about is a software buffer within the os kernel.
I think this problem only affects Quic, and they said Quic is not crucial, not used by a big percent of clients. We are many with Quic missconfigured on some nodes. Not a big deal. I have 2 on the oldest hardware.
Can you check the logs after you set these and reboot the machine?
I believe TrueNAS Scale is non-BSD type and TrusNAS Core is BSD type. So, I don’t know what version you use, but if it’s Core, you need to use the proper commands from those docs.
Because SNO should please the customers using the network and not throttle them. There will be no data to store if there will be no happy customers.
Sometimes I’m just amazed by how people are thinking.
Well, I guess if this will affect your 95th percentile or CIR you have with the carrier, then fair enough. But I doubt this for obvious reasons. Thus now, you are paying your ISP for a bandwidth you are not using. Smart.
My internet is a poor 100/40 Mbit copper line. Nothing else available here. Sometimes upload is close to saturation. So in fact it could make sense to reduce egress.
Nope. It would not. I have /20. Storagenode is allowed to consume all of it. Why not? Unused bandwidth – money down the drain.
If saturating upstream affects your other applications – then throttling anything is definitely is not the solution. You need some sort of smart queue management/fair queuing protocol on the upstream side.