Ok, so I added the partitions flag, going with
hadoop jar target/giraph-0.1-jar-with-dependencies.jar
org.apache.giraph.examples.SimpleShortestPathsVertex
-Dgiraph.SplitMasterWorker=false -Dgiraph.numComputeThreads=12
-Dhash.userPartitionCount=12 input output 12 1
but still I got no overall
To: user@giraph.apache.org
Subject: Re: What a worker really is and other interesting runtime information
Ok, so I added the partitions flag, going with
hadoop jar target/giraph-0.1-jar-with-dependencies.jar
org.apache.giraph.examples.SimpleShortestPathsVertex
-Dgiraph.SplitMasterWorker=false
@giraph.apache.org
*Subject:* Re: What a worker really is and other interesting runtime
information
** **
Ok, so I added the partitions flag, going with
hadoop jar target/giraph-0.1-jar-with-dependencies.jar
org.apache.giraph.examples.SimpleShortestPathsVertex
-Dgiraph.SplitMasterWorker
Daglis [mailto:alexandros.dag...@epfl.ch]
Sent: Thursday, November 29, 2012 12:30 PM
To: user@giraph.apache.org
Subject: Re: What a worker really is and other interesting runtime information
Hello Bence,
So, you have 96 cores at your disposal. My guess would be that 3 workers are
not enough to use
Oh, forgot one thing. You need to set the number of partitions to use
single each thread works on a single partition at a time.
Try -Dhash.userPartitionCount=number of threads
On 11/28/12 5:29 AM, Alexandros Daglis wrote:
Dear Avery,
I followed your advice, but the application seems to be
Hi Alexandros,
The extra task is for the master process (a coordination task). In your
case, since you are using a single machine, you can use a single task.
-Dgiraph.SplitMasterWorker=false
and you can try multithreading instead of multiple workers.
-Dgiraph.numComputeThreads=12
The
