IBM documentation usually has some excellent tips and tricks, and very well documented about how and why.
i already optimized my network setting a long time ago, but generally what i learned from that rabbit hole was that there are way to many bad suggestions about changing network setting for optimizing…
so my recommendation would be try to stick close to the defaults, if you like 10x or 100x a buffer sizes you might end up having problems emptying the buffer and stuff might sit for a long time, which can lead to all sorts of issues.
so do take all the optimizing suggestions online with a grain of salt, unless if you are learning about networking and want to learn the hard way…
the default are adopted because they work fine for most general purpose use cases.
and tho you might think you see an improvement short term from optimizing, its almost always at the cost of something else.
i’m sure what you used here is fine…
i saw somebody else said -w on sysctl would make it persistent, but i’m really unsure i did check
sysctl --help
which also seemed to indicate that to be the case… on top of that it’s a non critical thing, so even if it fails it doesn’t hurt anything really… so meh…
anyways since you doubted it i went and dug into the linux manual as suggest by the
sysctl --help
but as usual it’s futile because it has it’s own language… i mean how does this tell me if it is persistent or not…
-w, --write
Use this option when all arguments prescribe a key to be set.
if you do decided to test it out do let us know, if its persistent or not…
don’t really find the manual or --help very illuminating even if they sort of do indicate it without making it perfectly clear imo.