[ARROW-10351] [C++][Flight] See if reading/writing to gRPC get/put streams asynchronously helps performance

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: C++, FlightRPC
• External issue URL: https://github.com/apache/arrow/issues/26337
• Assignee: Unassigned
• Reporter: Wes McKinney
• Created: 20/Oct/20 02:57
• Updated: 11/Jan/23 08:12

Description

We don't use any asynchronous concepts in the way that Flight is implemented now, i.e. IPC deconstruction/reconstruction (which may include compression!) is not performed concurrent with moving FlightData objects through the gRPC machinery, which may yield suboptimal performance.

It might be better to apply an actor-type approach where a dedicated thread retrieves and prepares the next raw IPC message (within a Future) while the current IPC message is being processed – that way reading/writing to/from the gRPC stream is not blocked on the IPC code doing its thing.