Mailing-List: contact user-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@giraph.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.191.145.13
 which is an MX secondary for user@giraph.apache.org)
MIME-Version: 1.0
Date: Thu, 30 Apr 2015 13:58:55 -0700
Message-ID: 
 <CA+gAsQdR1JjAKVnz9ecyLsqPbkDwM6=WXKxWVRSFek4Lti2-zw@mail.gmail.com>
Subject: BSP Question to Giraph Developers
From: Arjun Sharma <as469613@gmail.com>
To: user@giraph.apache.org
Content-Type: multipart/alternative; boundary=001a11414af425f1a30514f75d8e

--001a11414af425f1a30514f75d8e
Content-Type: text/plain; charset=UTF-8

As we all know, Giraph is based on the BSP parallel computation model. My
question to Giraph developers is that what are the features or key
advantages of Giraph that were *only possible* because of the BSP model?

One aspect is scalability. Does the BSP model fundamentally contribute to
Giraph's scalability? How? One example is enabling the use of combiners
(because messages are sent at the same phase and hence can be combined),
but what else did you implement and relied on the assumption of BSP to make
Giraph more scalable?

Another aspect is usability. One benefit of the BSP model is touched by
Giraph users, as they only need to think in terms of phases of local
computation and network communication, which is simple enough. Do Giraph
developers get any advantage like that?

--001a11414af425f1a30514f75d8e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As we all know, Giraph is based on the BSP parallel comput=
ation model. My question to Giraph developers is that what are the features=
 or key advantages of Giraph that were *only possible* because of the BSP m=
odel?=C2=A0<div><br></div><div>One aspect is scalability. Does the BSP mode=
l fundamentally contribute to Giraph&#39;s scalability? How? One example is=
 enabling the use of combiners (because messages are sent at the same phase=
 and hence can be combined), but what else did you implement and relied on =
the assumption of BSP to make Giraph more scalable?<div><br></div><div>Anot=
her aspect is usability. One benefit of the BSP model is touched by Giraph =
users, as they only need to think in terms of phases of local computation a=
nd network communication, which is simple enough. Do Giraph developers get =
any advantage like that?</div><div><br></div><div><br></div><div><br></div>=
</div></div>

--001a11414af425f1a30514f75d8e--