You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/09 17:45:00 UTC

[jira] [Commented] (ARROW-2427) [C++] ReadAt implementations suboptimal

    [ https://issues.apache.org/jira/browse/ARROW-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430953#comment-16430953 ] 

ASF GitHub Bot commented on ARROW-2427:
---------------------------------------

pitrou opened a new pull request #1867: [WIP] ARROW-2427: [C++] Implement ReadAt properly
URL: https://github.com/apache/arrow/pull/1867
 
 
   Allow for concurrent I/O by avoiding locking and seeking.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> [C++] ReadAt implementations suboptimal
> ---------------------------------------
>
>                 Key: ARROW-2427
>                 URL: https://issues.apache.org/jira/browse/ARROW-2427
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>    Affects Versions: 0.9.0
>            Reporter: Antoine Pitrou
>            Priority: Major
>              Labels: pull-request-available
>
> The {{ReadAt}} implementations for at least {{OSFile}} and {{MemoryMappedFile}} take the file lock and seek. They could instead read directly from the given offset, allowing concurrent I/O from multiple threads.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)