[
https://issues.apache.org/jira/browse/GIRAPH-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102426#comment-13102426
]
Avery Ching commented on GIRAPH-28:
-----------------------------------
Thanks for isolating to the edge data only.
These numbers are much more reasonable =). Getting rid of the Edge class for
users (still useful for storing the requests) seems like an easy win for the
Object based Vertex (around a 20% memory reduction for edges). I think that
for many applications, using a pair of arrays might be reasonable and provide a
big win for memory reduction (i.e. page rank).
Now I'm really curious what was eating all the other memory though =)...
> Introduce new primitive-specific MutableVertex subclasses
> ---------------------------------------------------------
>
> Key: GIRAPH-28
> URL: https://issues.apache.org/jira/browse/GIRAPH-28
> Project: Giraph
> Issue Type: New Feature
> Components: graph
> Affects Versions: 0.70.0
> Reporter: Jake Mannix
> Assignee: Jake Mannix
> Attachments: GIRAPH-28.diff
>
>
> As discussed on the list,
> MutableVertex<LongWritable,DoubleWritable,FloatWritable,DoubleWritable> (for
> example) could be highly optimized in its memory footprint if the vertex and
> edge data were held in a form which minimized Java object usage.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
