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

Apurv Verma commented on HAMA-367:
----------------------------------

Hi Thomas,
 Apologies from my side also for not completing it completely.

I saw the changes. Looks perfect to me, everything seems to be taken care of. 
We no longer need 

{noformat}
setCompressMessage(boolean)
{noformat}

in BSPJob as Edward had asked. The user can choose not to specify this 
parameter "hama.messenger.compression.class" in site.xml in which case 
{noformat} CompressableMessageManager {noformat} would return a null and no 
compressor would be created.

No, snappy 0.2.0 should have been used, my mistake.

thanks, your design taught me many things.

+1 (It has been a long issue, I hope this is resolved now)

                
> Runtime Compression of BSP Messages to Improve the Performance
> --------------------------------------------------------------
>
>                 Key: HAMA-367
>                 URL: https://issues.apache.org/jira/browse/HAMA-367
>             Project: Hama
>          Issue Type: New Feature
>          Components: bsp, documentation 
>    Affects Versions: 0.4.0
>            Reporter: Edward J. Yoon
>            Assignee: Apurv Verma
>              Labels: gsoc, gsoc2011, mentor
>             Fix For: 0.5.0
>
>         Attachments: HAMA-367.patch, HAMA-367.patch, HAMA-367.patch, 
> HAMA-367_2.patch, test_files.tar.gz
>
>   Original Estimate: 2,016h
>  Remaining Estimate: 2,016h
>
> As you know, the exchanging data between processes, is a core part of whole 
> performance in Bulk Synchronous Parallel.
> In this research, we investigate BSP message data compression in the context 
> of large-scale distributed message-passing systems to reduce the 
> communication time of individual messages and to improve the bandwidth of the 
> overall system. 

--
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

        

Reply via email to