Hello Tripti,
I bumped into this mail, I am experiencing out-of-memory errors on my small
cluster,
and, as out-of-core graph does not seem to work on giraph 1.1-SNAPSHOT, I was
wondering if you had any jira / patched already posted to help solve this
issue ?
Thanks a lot
regards
Hi everyone,
I have two questions:
*Question 1)* I'm using release 1.1.0 and I'm really confused about the
fact that I'm having massive performance differences in the following
scenario. I need to send one message from each vertex to a subset of its
neighbors (all that satisfy a certain
Hi Matthew,
See class SendMessageToAllCache. Its in the same directory as
SendMessageCache. The first class is not used by Giraph unless you set
property giraph.oneToAllMsgSending to true.
Lukas
On 22.10.2014 20:10, Matthew Saltz wrote:
Hi everyone,
I have two questions:
*Question 1)*
Lukas,
Thank you so much for the help. By 'the first class', you mean
SendMessageToAllCache
is not used unless I set the property to true, right? Because I actually do
have giraph.oneToAllMsgSending=true, so if that means it's using
SendMessageToAllCache then everything makes much more sense. So
Following up, does anyone have thoughts re: MR1 vs YARN performance?
Thank you. -- matt
On Wed, Oct 22, 2014 at 8:34 AM, olivier.var...@orange.com wrote:
Hello Tripti,
I bumped into this mail, I am experiencing out-of-memory errors on my small
cluster,
and, as out-of-core graph does not
Actually, one more question: are there any disadvantages to enabling
oneToAllMessaging? Is there any reason not to do it by default?
Best,
Matthew
El 22/10/2014 23:28, Matthew Saltz sal...@gmail.com escribió:
Lukas,
Thank you so much for the help. By 'the first class', you mean
