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

Edward J. Yoon edited comment on HAMA-767 at 8/7/13 9:22 AM:
-------------------------------------------------------------

Just FYI, https://twitter.com/sscdotopen/status/311088184526266368

Basically I agree with him but I guess it's also a trade-off with the CPU and 
GC overheads. Anyway, Go to read the Stratosphere and Spark papers. 

And, Could you test how much space can be saved by Serialization? For example,

{code}Java Vertex Objects: 256MB vs. Serialized: ?MB{code}
                
      was (Author: udanax):
    Just FYI, https://twitter.com/sscdotopen/status/311088184526266368

Basically I agree with him but I guess it's also a trade-off with the CPU and 
GC overheads. Anyway, Go to read the Stratosphere and Spark papers. 

And, Could you test how much space can be saved by Serialization? For example,

{code}Java Objects: 256MB vs. Serialized: ?MB{code}

                  
> [GSoC 2013] Vertex addition and removal
> ---------------------------------------
>
>                 Key: HAMA-767
>                 URL: https://issues.apache.org/jira/browse/HAMA-767
>             Project: Hama
>          Issue Type: New Feature
>          Components: examples, graph
>    Affects Versions: 0.6.2
>            Reporter: Anastasis Andronidis
>            Assignee: Anastasis Andronidis
>              Labels: dynamic, graph, gsoc, gsoc2013, mentoring
>             Fix For: 0.6.3
>
>         Attachments: HAMA-767-v5.1.patch
>
>
> Implement addVertex and removeVertex methods for incremental graph support on 
> Graph API.

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

Reply via email to