> 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 t

> 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?