Hi,
We are also running Connected Components test with GraphX. We ran experiments
using Spark 1.6.1 on machine which have 16 cores with 2-way and run only a
single executor per machine. We got this result:
Facebook-like graph with 2^24 edges, using 4 executors with 90GB each, it took
100
Hi,
We are also running Connected Components test with GraphX. We ran experiments
using Spark 1.6.1 on machine which have 16 cores with 2-way and run only a
single executor per machine. We got this result:
Facebook-like graph with 2^24 edges, using 4 executors with 90GB each, it took
100
r@spark.apache.org>>
Subject: Re: GraphX performance and settings
I am not an expert but some thoughts inline
On Jun 16, 2016 6:31 AM, "Maja Kabiljo"
<majakabi...@fb.com<mailto:majakabi...@fb.com>> wrote:
>
> Hi,
>
> We are running some experiments with GraphX
I am not an expert but some thoughts inline
On Jun 16, 2016 6:31 AM, "Maja Kabiljo" wrote:
>
> Hi,
>
> We are running some experiments with GraphX in order to compare it with
other systems. There are multiple settings which significantly affect
performance, and we
Hi,
We are running some experiments with GraphX in order to compare it with other
systems. There are multiple settings which significantly affect performance,
and we experimented a lot in order to tune them well. I'll share here what are
the best we found so far and which results we got with