giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-262) Netty optimizations and bandwidth tracking
Date Tue, 17 Jul 2012 17:53:34 GMT

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

Avery Ching commented on GIRAPH-262:
------------------------------------

The idea behind ChannelRotator is that we can use multiple connections between clients and
servers and rotate the connections to possibly get better bandwidth (i.e. connection limited).
 I havn't experimented too much with it, but it does appear to make a difference in performance.
 The default is one connection between workers.

Handling requests locally improves performance nicely for small numbers of workers as 1/n
messages do not need to go over the network.

Additionally, I made the send/receive buffer sizes to be tunable as this seems to also impact
performance.
                
> Netty optimizations and bandwidth tracking
> ------------------------------------------
>
>                 Key: GIRAPH-262
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-262
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>         Attachments: GIRAPH-262.patch
>
>
> * Makes netty the default instead of HadoopRPC
> * Added optimization to handle requests locally when possible rather than go over the
network
> * Added TimedLogger to print only within a given time period
> * Added optimization for using multiple channels between clients/servers when bandwidth
is limited per connection
> * Added ByteCounter to track bandwidth across Netty (can be later integrated with GIRAPH-232).
> * Upgraded rat to 0.8 and excluded iml files (Intellij Idea)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message