You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/01/07 21:15:00 UTC

[jira] [Updated] (ARROW-15061) [C++] Add logging for kernel functions and exec plan nodes

     [ https://issues.apache.org/jira/browse/ARROW-15061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ARROW-15061:
-----------------------------------
    Labels: pull-request-available query-engine  (was: query-engine)

> [C++] Add logging for kernel functions and exec plan nodes
> ----------------------------------------------------------
>
>                 Key: ARROW-15061
>                 URL: https://issues.apache.org/jira/browse/ARROW-15061
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: C++
>            Reporter: Weston Pace
>            Assignee: Matthijs Brobbel
>            Priority: Major
>              Labels: pull-request-available, query-engine
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Using OT we should add spans that report the runtime of kernel functions.  We should  ensure that, if OT is disabled, there is no significant overhead.
> In addition we should add spans that report the runtime of each exec node.  This may be a little trickier than it would first seem because pipeline breakers like join, etc. don't do all of their work inside of InputReceived.  Those could potentially be added later in follow-up PRs if it is getting to be too tricky.  The simple nodes like FilterNode and ProjectNode should be more straightforward.  These spans should be the parent of any kernel functions launched by that node.
> There should also be a span for an entire exec plan run that will be the parent of all of this.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)