hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MaoYuan Xian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HAMA-761) Improvement for GraphJobMessage comparation operation
Date Sat, 08 Jun 2013 16:40:21 GMT

     [ https://issues.apache.org/jira/browse/HAMA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

MaoYuan Xian updated HAMA-761:
------------------------------

    Description: 
Currently, GraphJobMessage comparation opertion depends on the default comparator (org.apache.hadoop.io.WritableComparator
used), which has to read out all GraphJobMessage message (including vertexId and vertexValue)
when does the comparation. 
Since lots of comparation operations happen in graph computing, this limitation makes a performance
downgrade.

  was:
Currently, GraphJobMessage comparation opertion depends on the default comparator (org.apache.hadoop.io.WritableComparator
used), which has to read out all GraphJobMessage message (including key and value) when does
the comparation. 
Since lots of comparation operations happen in graph computing, this limitation makes a performance
downgrade.

    
> Improvement for GraphJobMessage comparation operation
> -----------------------------------------------------
>
>                 Key: HAMA-761
>                 URL: https://issues.apache.org/jira/browse/HAMA-761
>             Project: Hama
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 0.6.1
>            Reporter: MaoYuan Xian
>            Assignee: MaoYuan Xian
>
> Currently, GraphJobMessage comparation opertion depends on the default comparator (org.apache.hadoop.io.WritableComparator
used), which has to read out all GraphJobMessage message (including vertexId and vertexValue)
when does the comparation. 
> Since lots of comparation operations happen in graph computing, this limitation makes
a performance downgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message