Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Thu, 21 Mar 2013 19:03:15 +0000 (UTC)
From: "Alessandro Presta (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12638348.1363892499960.29093.1363892595706@arcas>
In-Reply-To: <JIRA.12638348.1363892499960@arcas>
References: <JIRA.12638348.1363892499960@arcas>
Subject: [jira] [Created] (GIRAPH-579) Make it possible to use different
 out-edges data structures for input and computation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alessandro Presta created GIRAPH-579:
----------------------------------------

             Summary: Make it possible to use different out-edges data structures for input and computation
                 Key: GIRAPH-579
                 URL: https://issues.apache.org/jira/browse/GIRAPH-579
             Project: Giraph
          Issue Type: New Feature
            Reporter: Alessandro Presta
            Assignee: Alessandro Presta


In some cases, the properties we want in the VertexEdges implementation during input may differ from the ones we want during computation.
Two examples:
1) During input, we want to keep only the top K edges according to weight, so we use a fixed-size min-heap. During computation, our algorithm needs fast random access, so we use a hash-map.
2) We have a VertexEdges implementation that's optimized for space and/or iteration speed, but has slow insertion. We can then use a different data structure that has fast insertion during input.
We can add an option to specify a different VertexEdges class to be used in EdgeStore during input.

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