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: domain of janlugt@gmail.com designates
 209.85.214.180 as permitted sender)
MIME-Version: 1.0
Sender: janlugt@gmail.com
Date: Tue, 10 Jul 2012 18:25:06 -0700
Message-ID: 
 <CAMOYj4A7yTO2j6oSNDsyGnryKv_WVkbCezZjvZcYE7Cf1-SXhA@mail.gmail.com>
Subject: Announcing: Green-Marl/Giraph
From: Jan van der Lugt <jan.van.der.lugt@oracle.com>
To: dev@giraph.apache.org, user@giraph.apache.org
Cc: Sungpack Hong <sungpack.hong@oracle.com>
Content-Type: multipart/alternative; boundary=f46d0444738393776c04c483b7fd

--f46d0444738393776c04c483b7fd
Content-Type: text/plain; charset=ISO-8859-1

Hi everyone,

Some of you might already know Green-Marl, Green-Marl compatibility was
even mentioned as a new feature for Giraph 0.2, but for those who don't,
let me give you a quick introduction.

Green-Marl is a domain-specific language tailored to graph algorithms. It
has many features that makes it possible to write graph algorithms very
concise and intuitive. For example, it has built-in constructs for graphs,
node properties, and traversals. A more complete description is given here:
http://ppl.stanford.edu/papers/asplos12_hong.pdf. Apart from the language,
there is also a Green-Marl compiler that compiles the language to different
targets. C++/OpenMP was initially supported, after which support for
Stanford GPS (a Pregel-clone developed at Stanford) was added for a subset
of the features in the Green-Marl language. The big advantage of using a
language like Green-Marl is that it enables you to write implicitly
parallel programs in an intuitive way with the compiler doing most of the
heavy work such as generating the messaging, converting pull-based
operation (remote reading) to push-based operations (message sending), etc.
In the last few months I have worked on a few features in Giraph that
enable Green-Marl to target Giraph as a back-end (namely GIRAPH-127,
GIRAPH-192 and GIRAPH-216). Since these have all been merged, Green-Marl
and Giraph should be compatible as of last week!

Using Green-Marl with Giraph is very simple, as long as you have a working
Hadoop/Giraph environment. Since the Green-Marl compiler is a
source-to-source compiler, it is very easy to use it in an existing set-up.
The steps to using Green-Marl are like this:

   1. Download the Green-Marl compiler from
   https://github.com/stanford-ppl/Green-Marl, run make_dirs.sh in the
   top-level dir and run make in the src dir. A more detailed explanation is
   given in the Github readme.
   2. Compile one of the examples (in the top-level directory) like
   this: bin/gm_comp -t=giraph apps/src/pagerank.gm
   3. Move pagerank.java to the Giraph src directory or your own project,
   package it into a .jar and go!
   4. Explore more examples, modify them and start writing your own

Green-Marl is actively being worked on within Oracle Labs, new features are
being added to the language (such as collection node properties) and
support for these features will be added to the distributed back-ends in
the near future.

In case of questions or suggestions, please send us a message! Feedback is
very much appreciated and people are more than welcome to contribute
everything from small bugfixes to entire back-ends ;-)

- Jan

--f46d0444738393776c04c483b7fd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi everyone,<div><br></div><div>Some of you might already know Green-Marl, =
Green-Marl compatibility was even mentioned as a new feature for Giraph 0.2=
, but for those who don&#39;t, let me give you a quick introduction.</div>


<div><br></div><div>Green-Marl is a domain-specific language tailored to gr=
aph algorithms. It has many features that makes it possible to write graph =
algorithms very concise and intuitive. For example, it has built-in constru=
cts for graphs, node properties, and traversals. A more complete descriptio=
n is given here:=A0<a href=3D"http://ppl.stanford.edu/papers/asplos12_hong.=
pdf" target=3D"_blank">http://ppl.stanford.edu/papers/asplos12_hong.pdf</a>=
. Apart from the language, there is also a Green-Marl compiler that compile=
s the language to different targets. C++/OpenMP was initially supported, af=
ter which support for Stanford GPS (a Pregel-clone developed at Stanford) w=
as added for a subset of the features in the Green-Marl language. The big a=
dvantage of using a language like Green-Marl is that it enables you to writ=
e implicitly parallel programs in an intuitive way with the compiler doing =
most of the heavy work such as generating the messaging, converting pull-ba=
sed operation (remote reading) to push-based operations (message sending), =
etc.</div>
<div>In the last few months I have worked on a few features in Giraph that =
enable Green-Marl to target Giraph as a back-end (namely GIRAPH-127, GIRAPH=
-192 and GIRAPH-216). Since these have all been merged, Green-Marl and Gira=
ph should be compatible as of last week!</div>

<div><br></div><div>Using Green-Marl with Giraph is very simple, as long as=
 you have a working Hadoop/Giraph environment. Since the Green-Marl compile=
r is a source-to-source compiler, it is very easy to use it in an existing =
set-up. The steps to using Green-Marl are like this:</div>

<div><ol><li>Download the Green-Marl compiler from=A0<a href=3D"https://git=
hub.com/stanford-ppl/Green-Marl" target=3D"_blank">https://github.com/stanf=
ord-ppl/Green-Marl</a>, run make_dirs.sh in the top-level dir and run make =
in the src dir. A more detailed explanation is given in the Github readme.<=
/li>

<li>Compile one of the examples (in the top-level directory) like this:=A0b=
in/gm_comp -t=3Dgiraph apps/src/<a href=3D"http://pagerank.gm">pagerank.gm<=
/a></li><li>Move pagerank.java to the Giraph src directory or your own proj=
ect, package it into a .jar and go!</li>
<li>Explore more examples, modify them and start writing your own</li>
</ol><div>Green-Marl is actively being worked on within Oracle Labs, new fe=
atures are being added to the language (such as collection node properties)=
 and support for these features will be added to the distributed back-ends =
in the near future.</div>
<div><br></div><div>In case of questions or suggestions, please send us a m=
essage! Feedback is very much appreciated and people are more than welcome =
to contribute everything from small bugfixes to entire back-ends ;-)</div>
<div><br></div><div>- Jan</div><div><br></div></div>

--f46d0444738393776c04c483b7fd--