3 ms·
There are many ways to improve on TCP for specific use cases. You can get maybe another 10%-20% of performance, as Google did with QUIC. Used outside that use c
by Animats 4y ago
There are many ways to improve on TCP for specific use cases. You can get maybe another 10%-20% of performance, as Google did with QUIC. Used outside that use case, performance may be worse. The design goal of TCP was that it should Just Work. It needed to be interoperable between different vendors, provide reasonably good performance, work over a wide range of networks speeds, work over possibly flaky networks, continue to perform under overload, and not have manual tuning parameters. It does well against those criteria.
This new protocol the sort of thing Osterholt is known for. He came up with "log" file systems, which are optimized for the case where disk writes outnumber reads. Reading then requires more seeks on mechanical drives. If you're mostly writing logs that are seldom read, it's a win. If you're doing more reading than writing, it's a lose.
- toast0 4y ago> There are many ways to improve on TCP for specific use cases. You can get maybe another 10%-20% of performance, as Google did with QUIC. Most of the gains of QUIC are in exchanging data with the first round trip, which you can do with TCP fast open as long as middleboxes don't mess it up; different congestion control, which you could do in TCP if you control the OS on the sending side as long as the middle doesn't mess it up, which shouldn't happen in a data center; and maybe some benefits for connection switching, which should hopefully not be necessary in a data center (although I've certainly seen cases it would help!); multi-path TCP also addresses this, but has probably worse CPU efficiency problems: if a logical flow is coming in on multiple NIC queues, there's going to be cross-cpu communication on the data structures. Unless it's changed, QUIC also simply won't handshake if the path MTU is too small, so you don't get to have the excitement of path MTU discovery failures; but you really shouldn't have that problem in a datacenter.