You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2020/05/19 13:19:00 UTC

[jira] [Updated] (ARROW-8847) [C++] Pass task size / metrics in Executor API

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

Antoine Pitrou updated ARROW-8847:
----------------------------------
    Description: 
For now, our ThreadPool implementation would ignore those metrics, but other implementations may use it for custom ordering.

Example metrics:
* IO size (number of bytes)
* CPU cost (~ number of instructions)
* Whether it's CPU-bound or IO-bound
* Priority (opaque integer? lower is more urgent)



  was:
For now, our ThreadPool implementation would ignore those metrics, but other implementations may use it for custom ordering.

Example metrics:
* IO size (number of bytes)
* CPU cost (~ number of instructions)
* Priority (opaque integer? lower is more urgent)




> [C++] Pass task size / metrics in Executor API
> ----------------------------------------------
>
>                 Key: ARROW-8847
>                 URL: https://issues.apache.org/jira/browse/ARROW-8847
>             Project: Apache Arrow
>          Issue Type: Wish
>          Components: C++
>            Reporter: Antoine Pitrou
>            Assignee: Antoine Pitrou
>            Priority: Major
>
> For now, our ThreadPool implementation would ignore those metrics, but other implementations may use it for custom ordering.
> Example metrics:
> * IO size (number of bytes)
> * CPU cost (~ number of instructions)
> * Whether it's CPU-bound or IO-bound
> * Priority (opaque integer? lower is more urgent)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)