Re: Giraph automated parameter tuning

Hi Muaz, this is a very interesting topic! First of all, the top 2 (number of workers, heap size) are indeed the most important. Also, I think giraph.numComputeThreads and probably the netty-related thread parameter are more important. The following are less important: - giraph.maxMutationsPerR

Re: Is it normal that a same algorithm for 4 profiles calculus implemented both in giraph and graphlab gives different output with same input?

you know > ... thanks for interesting in my work! > > Il giorno gio 9 ago 2018 alle ore 01:03 Dionysios Logothetis < > dlogothe...@gmail.com> ha scritto: > >> Hi Francesco, >> >> Here are few thoughts on reasons this may happen: >> >> - I hav

Re: Is it normal that a same algorithm for 4 profiles calculus implemented both in giraph and graphlab gives different output with same input?

Hi Francesco, Here are few thoughts on reasons this may happen: - I haven't written any graphlab application myself, but the synchronous vs. asynchronous model can generally be a reason for differences. It is possible that such differences do not manifest on smaller graphs. What's the size of the

Re: giraph compile error

I am able to run mvn -Phadoop_2 -fae -DskipTests clean install on MacOS, Maven 3.5.0, Java 1.8.0_131 and on CentOS, Maven 3.3.9, Java 1.8.0_60 I'll take it there's nothing earlier in the build log that may indicate an issue? On Sun, Aug 5, 2018 at 6:43 AM, Thomas Rummler wrote: > Hi, I got