You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:03 UTC

[jira] [Assigned] (ARROW-15732) [C++] Do not use any CPU threads in execution plan when use_threads is false

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

Todd Farmer reassigned ARROW-15732:
-----------------------------------

    Assignee:     (was: Weston Pace)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [C++] Do not use any CPU threads in execution plan when use_threads is false
> ----------------------------------------------------------------------------
>
>                 Key: ARROW-15732
>                 URL: https://issues.apache.org/jira/browse/ARROW-15732
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Weston Pace
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, scan operations that supply use_threads=false will use 1 CPU thread, the calling thread, and some # of I/O threads.  We should remove that CPU thread from being used.
> It is being used at the moment because we need something to transfer work onto when asynchronous I/O tasks complete.  We can fix this by allowing a serial executor to run an async generator (creating an iterator).  This will also allow us to change the execution plan so that it always expects an executor to be present which should simplify the logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)