[
https://issues.apache.org/jira/browse/HADOOP-18028?focusedWorklogId=748535&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-748535
]
ASF GitHub Bot logged work on HADOOP-18028:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Mar/22 10:57
Start Date: 28/Mar/22 10:57
Worklog Time Spent: 10m
Work Description: pjfanning edited a comment on pull request #4109:
URL: https://github.com/apache/hadoop/pull/4109#issuecomment-1079981138
@steveloughran twitter futures should be fairly easily replaced with [Java
futures](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/Future.html)
* this seems to a fairly good description of the twitter FuturePool -
https://blog.knoldus.com/twitter-future-in-scala/
* should be possible to port it to Java easily enough
* it may even not be necessary to port the twitter FuturePool because it
appears its main use to help Scala users avoid having to deal Java futures used
in AWS code (cf
https://medium.com/@sveinnfannar/thread-pooling-in-scala-using-twitter-s-futurepool-8f38c6448fa2)
I have an example change - https://github.com/steveloughran/hadoop/pull/2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 748535)
Time Spent: 13.5h (was: 13h 20m)
> High performance S3A input stream with prefetching & caching
> ------------------------------------------------------------
>
> Key: HADOOP-18028
> URL: https://issues.apache.org/jira/browse/HADOOP-18028
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Bhalchandra Pandit
> Assignee: Bhalchandra Pandit
> Priority: Major
> Labels: pull-request-available
> Time Spent: 13.5h
> Remaining Estimate: 0h
>
> I work for Pinterest. I developed a technique for vastly improving read
> throughput when reading from the S3 file system. It not only helps the
> sequential read case (like reading a SequenceFile) but also significantly
> improves read throughput of a random access case (like reading Parquet). This
> technique has been very useful in significantly improving efficiency of the
> data processing jobs at Pinterest.
>
> I would like to contribute that feature to Apache Hadoop. More details on
> this technique are available in this blog I wrote recently:
> [https://medium.com/pinterest-engineering/improving-efficiency-and-reducing-runtime-using-s3-read-optimization-b31da4b60fa0]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
