bkietz opened a new pull request #9712: URL: https://github.com/apache/arrow/pull/9712
Also added a unit test and some notes to `benchmarks.rst`. My own preferred benchmarking workflow is to exclusively output run results to json and run `archery benchmark diff` against those. I'm not sure that automatic (re)generation and rebuild of the cmake build directory is a good default; IMO a new user will most likely be trying to iterate rather than make a single shot run and should be protected from staring at a release build log after every change. Is there enough guidance in `benchmarks.rst`? @dianaclarke @edponce ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
