3 ms·
> I think this is one of the rare cases where I'd prefer if the kernel had a "magic" setting... All this stuff should be automatic. The problem is that it can
by Animats 3y ago
> I think this is one of the rare cases where I'd prefer if the kernel had a "magic" setting...
All this stuff should be automatic. The problem is that it can take a few round trips to discover what the application is doing. This comes up with "slow start", where you need some time to discover what's going on. In a world of short-lived HTTP connections, self-adjusting algorithms don't have time to self-adjust before exit.
A delayed ACK is a bet. You're betting that the other end is going to respond with useful data before the delayed ACK timer runs out. If it does, you won the bet. If it doesn't, you lost. Nothing checks whether you're on a losing streak. But it takes a few round trips to make that decision.
When I was working on this, the object was to get from appallingly bad to acceptable performance without too much complexity. Today, people crank up things like HTTP/3 to get a few percent more performance at the cost of greatly increased complexity.
- bhaney 3y ago> In a world of short-lived HTTP connections, self-adjusting algorithms don't have time to self-adjust before exit We could potentially have the kernel group these heuristics to a process or process group, since there's no real reason to live in the network stack and have its context restricted to a single connection. Like, if most packets on a system are being generated by a few nginx processes, and most of them seem to be tiny (or are on a losing streak for any other kind of bet), enable Nagle's (or any other relevant optimization) for any connections those nginx processes create?
- Animats 3y agoYes, and then you need a UI and a dashboard and an alarm system and a policy deployment manager and a ... As you go for the last 10% of performance, the complexity climbs rapidly.
- GoblinSlayer 3y agoReset packet injection is popular in the wild, so I'm optimistic about tip to toe authenticated UDP transports, also less retarded congestion control that doesn't take network down just to see if it will break. Complexity can be moved to a proxy, and simple applications don't care about tuning anyway.