GitHub user hbdeshmukh opened a pull request:
https://github.com/apache/incubator-quickstep/pull/36
QUICKSTEP-24 Report generation support for work order execution statistics
This PR provides an initial version of the support required to report
individual work order execution performance. Some highlights are described
below:
- A flag to enable work order profiling report generation.
- At the end of each query, a report is generated which includes worker
ID, its NUMA socket, the operator that produced the WorkOrder and the
execution time in microseconds.
- The output is printed on stdout in CSV format as of now.
As this is a rudimentary support for the functionality, there is a lot of
future work in this regards, which includes printing of CPU core information,
printing operator name, allowing user to specify a file where the output can be
written, extend the support for rebuild WorkOrder statistics etc.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-quickstep
workorder-time-reporting
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quickstep/pull/36.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #36
----
commit 3d1a4be275d84ae10236877e1a3e85006fe70159
Author: Harshad Deshmukh <[email protected]>
Date: 2016-06-16T19:03:34Z
Basic support to report individual work order profiling results
- A flag to enable work order profiling report generation.
- At the end of each query, a report is generated which includes worker
ID, its NUMA socket, the operator that produced the WorkOrder and the
execution time in microseconds.
- The output is printed on stdout in CSV format as of now.
- As this is a rudimentary support for the functionality, there is a lot of
future work in this regards, which includes printing of CPU core
information,
printing operator name, allowing user to specify a file where the output
can
be written etc.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---