[
https://issues.apache.org/jira/browse/HDFS-7966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623778#comment-14623778
]
Duo Zhang commented on HDFS-7966:
---------------------------------
And there is a good news, in {{TestHttp2RandomReadPerformance}}, HTTP/2
implementation beats the old implementation. We create 4000 connections to one
datanode, and use one thread to peek a connection and read a small chunk of
data sequentially.
The result is
{noformat}
******* time based on http2 124ms
******* time based on tcp 274ms
{noformat}
And 5000 connections will cause OOM(can not create thread) in the tcp test. I
think this is reasonable since NIO based framework has much less threads than
OIO.
I'm busy these days so only have some time at weekend. Will do these tests on a
cluster ASAP. Thanks.
> New Data Transfer Protocol via HTTP/2
> -------------------------------------
>
> Key: HDFS-7966
> URL: https://issues.apache.org/jira/browse/HDFS-7966
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Haohui Mai
> Assignee: Qianqian Shi
> Labels: gsoc, gsoc2015, mentor
> Attachments: GSoC2015_Proposal.pdf,
> TestHttp2LargeReadPerformance.svg, TestHttp2Performance.svg
>
>
> The current Data Transfer Protocol (DTP) implements a rich set of features
> that span across multiple layers, including:
> * Connection pooling and authentication (session layer)
> * Encryption (presentation layer)
> * Data writing pipeline (application layer)
> All these features are HDFS-specific and defined by implementation. As a
> result it requires non-trivial amount of work to implement HDFS clients and
> servers.
> This jira explores to delegate the responsibilities of the session and
> presentation layers to the HTTP/2 protocol. Particularly, HTTP/2 handles
> connection multiplexing, QoS, authentication and encryption, reducing the
> scope of DTP to the application layer only. By leveraging the existing HTTP/2
> library, it should simplify the implementation of both HDFS clients and
> servers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
