|
|
|
|
|
by SaveTheRbtz
1860 days ago
|
|
The analysis itself is quite impressive: a very systematic top-down approach. We need more people doing stuff like this! But! Be careful applying tunables from the article "as-is"[1]: some of them would destroy TCP performance: net.ipv4.tcp_sack=0
net.ipv4.tcp_dsack=0
net.ipv4.tcp_timestamps=0
net.ipv4.tcp_moderate_rcvbuf=0
net.ipv4.tcp_congestion_control=reno
net.core.default_qdisc=noqueue
Not to mention that `gro off` that will bump CPU usage by ~10-20% on most real world workload, Security Team would be really against turning off mitigations, and usage of `-march=native` will cause a lot of core dumps in heterogenous production environments.[1] This is usually the case with single purpose micro-benchmarks: most of the tunables have side effects that may not be captured by a single workflow. Always verify how the "tunings" you found on the internet behave in your environment. |
|