Return-Path: X-Original-To: apmail-giraph-user-archive@www.apache.org Delivered-To: apmail-giraph-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46B0817B21 for ; Mon, 10 Nov 2014 04:00:40 +0000 (UTC) Received: (qmail 22157 invoked by uid 500); 10 Nov 2014 04:00:39 -0000 Delivered-To: apmail-giraph-user-archive@giraph.apache.org Received: (qmail 22093 invoked by uid 500); 10 Nov 2014 04:00:39 -0000 Mailing-List: contact user-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@giraph.apache.org Delivered-To: mailing list user@giraph.apache.org Received: (qmail 22080 invoked by uid 99); 10 Nov 2014 04:00:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2014 04:00:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vincentiusmartin@gmail.com designates 209.85.192.172 as permitted sender) Received: from [209.85.192.172] (HELO mail-pd0-f172.google.com) (209.85.192.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2014 04:00:13 +0000 Received: by mail-pd0-f172.google.com with SMTP id r10so6989155pdi.31 for ; Sun, 09 Nov 2014 20:00:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=u4QzvmVvog+hxCV+xxNA4TE2W03QztTFWP596cmnOfk=; b=tnD6fXx+mfKMJsEkUwDvlqlxOOsPPHsG7fZFa9jKHbiFmpLfCzZJzaXM3TKhFAYVxe zDHV4y5HsD1khajyNeWIEug/CTReQ/e/C+pkliOGREfdJbl22fWnB9wOYxb/xHpnxoz1 GwPw3YpVoplL80bto2v3807cTKlx2afqDosLmaFn91endpMRCx08zKlJRYHuVH6rxr6O AYfaZC2nEhzftjfOGaMLdVIkePbPe+9I0RjBpAlMVgoTPxG6rJwB9FLHqU0Gr/NvoT8u vLjglBlJqN4g+sMu3+0/09Y19JiSeSnIWZt6lFEY0aptK5JPqX34EkbCpN1gsiegmRMa fZjQ== MIME-Version: 1.0 X-Received: by 10.69.1.34 with SMTP id bd2mr29025013pbd.67.1415592011876; Sun, 09 Nov 2014 20:00:11 -0800 (PST) Received: by 10.70.97.18 with HTTP; Sun, 9 Nov 2014 20:00:11 -0800 (PST) Date: Mon, 10 Nov 2014 11:00:11 +0700 Message-ID: Subject: When do Giraph vertices receive their messages? From: Vincentius Martin To: user@giraph.apache.org Content-Type: multipart/alternative; boundary=047d7b16050f03ce510507793373 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b16050f03ce510507793373 Content-Type: text/plain; charset=UTF-8 I am curious about how does Giraph receive messages before processing it I know that they use their accepted messages in the compute() method on the next superstep, but when do they receive it? If it is before the checkpoint process, is there any part in the documentation/code that I can see to understand it? Also, what mechanism that Giraph use to store messages before superstep S+1? Are they store it in a buffer or disk first? I still cannot find anything about this. Regards, Vincentius Martin --047d7b16050f03ce510507793373 Content-Type: text/html; charset=UTF-8
I am curious about how does Giraph receive messages before processing it

I know that they use their accepted messages in the compute() method on the next superstep, but when do they receive it? If it is before the checkpoint process, is there any part in the documentation/code that I can see to understand it?

Also, what mechanism that Giraph use to store messages before superstep S+1? Are they store it in a buffer or disk first?

I still cannot find anything about this.


Regards,
Vincentius Martin
--047d7b16050f03ce510507793373--