Jakob Homan updated GIRAPH-139:

    Attachment: GIRAPH-139.patch

Patch that makes the page rank benchmark accessible from bin/giraph.  The 
default is the edgelist-based vertex, but the hashmap-based vertex is available 
as a separate class.  Calling the example is a bit hairy, since it's now not 
restricted to just the pseudoinputformat:

{noformat} bin/giraph \n
-DPageRankBenchmark.superstepCount=200 \n
-DpseudoRandomVertexReader.aggregateVertices=220 \n
-DpseudoRandomVertexReader.edgesPerVertex=37 \n
lib/giraph-0.2-SNAPSHOT.jar \n
org.apache.giraph.benchmark.HashMapPageRankBenchmark \n -w 10 \n 
-if org.apache.giraph.benchmark.PseudoRandomVertexInputFormat \n 
-of org.apache.giraph.lib.AdjacencyListTextVertexOutputFormat \n 
-op benchmark_results
I'm thinking that allowing vertices to provide default in/outputformat via 
annotations may be a way to avoid some of this extra text.

Tests, javadoc and rat passes (except rat complains about CODE_CONVENTIONS, 
which is out of scope of this JIRA).

Once this is committed, we need to update the wiki...
> Change PageRankBenchmark to use be accessible via bin/giraph
> ------------------------------------------------------------
>                 Key: GIRAPH-139
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-139
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: GIRAPH-139.patch
> Currently the PageRankBenchmark has its own main and tool implementation and 
> is difficult to access from the bin/giraph script.  It would be better if 
> everything were accessible via bin/giraph.  The benchmark is particularly 
> problematic because it uses inner classes for its two actual Vertex 
> implementations, which have to be specified on the command line as their 
> .class name(ie 
> org.apache.giraph.benchmark.PageRankBenchmark$PageRankHashMapVertex) rather 
> than just with dots, as one would expect.

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