You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2021/03/17 10:27:00 UTC

[jira] [Resolved] (ARROW-11907) [C++] Use our own executor in S3FileSystem

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

Antoine Pitrou resolved ARROW-11907.
------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 9678
[https://github.com/apache/arrow/pull/9678]

> [C++] Use our own executor in S3FileSystem
> ------------------------------------------
>
>                 Key: ARROW-11907
>                 URL: https://issues.apache.org/jira/browse/ARROW-11907
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: C++
>            Reporter: Antoine Pitrou
>            Assignee: Antoine Pitrou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> We use the AWS SDK async APIs in some places in S3FileSystem, but all they do is spawn a separate thread and run the sync API in it.
> Instead we should use our IO executor, which would:
> 1) put an upper bound on the number of threads started
> 2) (presumably) reduce latency by reusing threads instead of spawning a throwaway thread for each async call
> 3) allow for cancellation



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