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

ASF GitHub Bot commented on HADOOP-17250:
-----------------------------------------

github-actions[bot] commented on PR #2307:
URL: https://github.com/apache/hadoop/pull/2307#issuecomment-3634837256

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> ABFS: Random read perf improvement
> ----------------------------------
>
>                 Key: HADOOP-17250
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17250
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.3.0
>            Reporter: Sneha Vijayarajan
>            Assignee: Mukund Thakur
>            Priority: Major
>              Labels: abfsactive, pull-request-available
>             Fix For: 3.3.2
>
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> Random read if marginally read ahead was seen to improve perf for a TPCH 
> query. 
>  
> Introducing fs.azure.readahead.range parameter which can be set by user.
> Data will be populated in buffer for random reads as well which leads to 
> lesser
> remote calls.
> This patch also changes the seek implementation to perform a lazy seek. Actual
> seek is done when a read is initiated and data is not present in buffer else
> date is returned from buffer thus reducing the number of remote calls.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to