[C++] Measure microperformance associated with ExecBatchIterator

[asfimport]

arrow::compute::ExecBatch uses a vector of arrow::Datum to contain a collection of ArrayData and Scalar objects for kernel execution. It would be helpful to know how many nanoseconds of overhead is associated with basic interactions with this data structure to know the cost of using our vendored variant, and other such issues.

Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney / @wesm

Related issues:

• [C++] C++ array kernels framework and execution buildout (umbrella issue) (is a child of)
• [C++] Query engine umbrella issue (is a child of)

PRs and other links:

• GitHub Pull Request #9280

_{Note: This issue was originally created as ARROW-8928. Please see the migration documentation for further details.}

[asfimport]

Ben Kietzman / @bkietz:
ARROW-12010 adds KeyColumnData which is a simplified non-owning wrapper for non-nested ArrayData. Reusing it for ExecBatch's values would be a worthwhile optimization

[asfimport]

Neal Richardson / @nealrichardson:
@bkietz @michalursa either of you interested in picking this up? Or should we close?

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 9280
#9280