[ https://issues.apache.org/jira/browse/HADOOP-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987944#comment-16987944 ]
Janus Chow commented on HADOOP-13144: ------------------------------------- The result is not very good. With default implementation, the average processingTime of Routers is about 10ms, with multi connection, the average processingTime can get 20ms. Do you have any other suggestions on how to reduce the proxyAvg of routers? The processingAvg is low, but the proxyAvg is quite high in production. > Enhancing IPC client throughput via multiple connections per user > ----------------------------------------------------------------- > > Key: HADOOP-13144 > URL: https://issues.apache.org/jira/browse/HADOOP-13144 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc > Reporter: Jason Kace > Assignee: Íñigo Goiri > Priority: Minor > Attachments: HADOOP-13144-performance.patch, HADOOP-13144.000.patch, > HADOOP-13144.001.patch, HADOOP-13144.002.patch, HADOOP-13144.003.patch > > > The generic IPC client ({{org.apache.hadoop.ipc.Client}}) utilizes a single > connection thread for each {{ConnectionId}}. The {{ConnectionId}} is unique > to the connection's remote address, ticket and protocol. Each ConnectionId > is 1:1 mapped to a connection thread by the client via a map cache. > The result is to serialize all IPC read/write activity through a single > thread for a each user/ticket + address. If a single user makes repeated > calls (1k-100k/sec) to the same destination, the IPC client becomes a > bottleneck. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org