Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Wed, 4 Jun 2014 16:07:02 +0000 (UTC)
From: "Pavan Kumar (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12711879.1398996330768.70945.1401898022709@arcas>
In-Reply-To: <JIRA.12711879.1398996330768@arcas>
References: <JIRA.12711879.1398996330768@arcas>
Subject: [jira] [Commented] (GIRAPH-892) Add support for new vertexIdData
 based data structures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pavan Kumar commented on GIRAPH-892:
------------------------------------

Discarded old review & created a new one
https://reviews.apache.org/r/22238/
with GIRAPH-907 as its parent

> Add support for new vertexIdData based data structures
> ------------------------------------------------------
>
>                 Key: GIRAPH-892
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-892
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Pavan Kumar
>            Assignee: Pavan Kumar
>         Attachments: GIRAPH-892.patch, GIRAPH-892_1.patch
>
>
> Currently writableRequests are deserialized from network buffers into a bytearray based datastructure (vertexIdData - ByteArrayVertexIdEdges, ByteArrayVertexIdMessages, etc.) and then immediately stored into MessageStore, EdgeStore, etc. 
> In this diff we ensure that we can directly read from network buffers (while storing in MessageStore for example) without creating an (unnecessary intermediate ByteArray based) vertexIdData object.


--
This message was sent by Atlassian JIRA
(v6.2#6252)