incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (HAMA-380) Send messages in batches to reduce RPC overhead.
Date Mon, 18 Apr 2011 15:55:06 GMT


Hudson commented on HAMA-380:

-1 overall.  Here are the results of testing the latest attachment
against trunk revision 1090506.

    @author +1.  The patch does not contain any @author tags.

    tests included -1.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new javac compiler warnings.

    release audit +1.  The applied patch does not generate any new release audit warnings.

    findbugs -1.  The patch appears to cause Findbugs to fail.

    core tests +1.  The patch passed core unit tests.

Test results:
Checkstyle results:
Console output:

This message is automatically generated.

> Send messages in batches to reduce RPC overhead.
> ------------------------------------------------
>                 Key: HAMA-380
>                 URL:
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp
>    Affects Versions: 0.3.0
>            Reporter: Miklos Erdelyi
>             Fix For: 0.3.0
>         Attachments: bspmsgbundle.patch, bspmsgbundle.v2.patch
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> When profiling graph computations running on HAMA it turned out that huge amount of time
is spent in RPC calls.
> To reduce this overhead I propose extending the GroomServer's API with a put(BSPMessageBundle)
method so that a group of messages can be transferred from the caller to the callee at once.
Also, the sync() operation should be improved by sending messages in batches rather than one-by-one.
> Using BSPMessageBundle makes it easier to add support for compression of messages later.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message