It seems like this discussion would be relevant to the gRPC community. There are probably other issues at play, like ensuring that multiple streams through the same port do not block each other too much if one stream has messages of smaller size and another larger size, then the byte slices sent are broken up into smaller pieces. We may want to make some improvements to gRPC to configure it to better suit our performance requirements
On Sun, Feb 24, 2019 at 1:19 PM Antoine Pitrou <anto...@python.org> wrote: > > > Le 24/02/2019 à 19:46, Wes McKinney a écrit : > > OK, I don't know enough about sockets or networking to know what > > hypothetical performance is possible with 16 concurrent packet streams > > going through a single port (was the 5GB/s based on a single-threaded > > or multithreaded benchmark? i.e. did it simulate the the equivalent > > number / size / concurrency of packets that the Flight benchmark is > > doing). > > The 5 GB/s uses just two threads: one server thread, one client thread. > The code is almost trivial, it's just careful to avoid spurious copies: > https://gist.github.com/pitrou/86fd433a8f71b0052e29fddcf4d766be > > Regards > > Antoine.
