Weston Pace created ARROW-15059:
-----------------------------------
Summary: [C++] Add basic visibility into execution engine
performance
Key: ARROW-15059
URL: https://issues.apache.org/jira/browse/ARROW-15059
Project: Apache Arrow
Issue Type: Improvement
Components: C++
Reporter: Weston Pace
For internal development purposes and for bug reports and highly technical
users it will be extremely helpful if we can turn on and off a profiling log.
I think initially:
* We may want the ability to entirely disable logging with a compile-time
variable
* Enabling or disabling the log is controlled by an environment variable
(assuming we built with logging)
* The log will initially just dump to stdout or a flat file (we can also or
will also someday export via OT)
* Some initial metrics include "run time of node", "run time of kernel
function", "run time of query"
* It would be nice if we could get some regular statistics as well such as the
allocated bytes of the memory pools, RSS consumed by the process, etc. Perhaps
that would require two files.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
