Mailing-List: contact giraph-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: giraph-dev@incubator.apache.org
Date: Mon, 12 Sep 2011 06:01:13 +0000 (UTC)
From: "Severin Corsten (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <6006622.16160.1315807273163.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1291101410.6990.1315549389003.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (GIRAPH-28) Introduce new primitive-specific
 MutableVertex subclasses
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Severin Corsten commented on GIRAPH-28:
---------------------------------------

I think this is a good idea. The most common use of the OutEdgeMap is to iterate over the values. The Map doesn't bring any additional information. 

And I like Jakes idea bud I don't know whether it brings any advantage and should be implemented in addition to a getter.


> 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