4 ms·
The collapsing and pruning of tcp buffers shows up in network statistics also, could have been the first hint. ‣ netstat -s | grep -E '(prune|collap)'
by r4um 11y ago
The collapsing and pruning of tcp buffers shows up in network statistics also, could have been the first hint.
‣ netstat -s | grep -E '(prune|collap)'
233 packets pruned from receive queue because of socket buffer overrun
1581 packets collapsed in receive queue due to low socket buffer
Usually system defaults work just fine, unless you want to tune for a very specific type of workload.
- majke 11y agoLooking at netstat makes sense as long as the numbers are low. It's hard to correlate one of 167 counters to the unpredictable latency event you are just debugging :) $ netstat -s | grep -E '(prune|collap)' 4445504 packets pruned from receive queue because of socket buffer overrun 150606 packets pruned from receive queue 278333723 packets collapsed in receive queue due to low socket buffer