Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Mon, 10 Jun 2013 06:53:20 +0000 (UTC)
From: "Nitay Joffe (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12651655.1370599357477.92795.1370847200409@arcas>
In-Reply-To: <JIRA.12651655.1370599357477@arcas>
References: <JIRA.12651655.1370599357477@arcas>
Subject: [jira] [Updated] (GIRAPH-683) Jython for Computation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GIRAPH-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nitay Joffe updated GIRAPH-683:
-------------------------------

    Description: 
Support for writing Computation code in Python. We add Jython bindings so that the Python computation code can communicate back with the Java Giraph classes.

To make this work I had to change a few parts of Giraph:
1) The Jython computation is not known until we read the script and create a Computation object for it at runtime. This has to be done on each worker separately after the job has launched. Because of this, there is no Computation class set at the beginning. I suspect other scripting languages will have similar issue. To fix this I created a ComputationFactory interface which is responsible for creating the Computation, with a default that just grabs the class from the Configuration and creates it.
2) I created a GiraphTypes class to hold the I,V,E,M1,M2 classes. There was a lot of repetitive code around these things so centralizing it all in one place made things a lot cleaner.
3) I added some more helpers like isDefaultValue() to our conf options.

This patch contains our page rank benchmark implementation in Jython. I added an option (--jython) which chooses whether to run the default or the jython version.

To use Jython all the user has to do is call Jython#init(...) somewhere in his initialization.

Here is the initial comparison (4 workers, 10M vertices, 25 edges per vertex):

Java:
Total (milliseconds)	104,388	0	104,388
Superstep 3 (milliseconds)	16,750	0	16,750
Setup (milliseconds)	2,895	0	2,895
Shutdown (milliseconds)	50	0	50
Superstep 0 (milliseconds)	15,838	0	15,838
Superstep 4 (milliseconds)	19,088	0	19,088
Input superstep (milliseconds)	8,700	0	8,700
Superstep 5 (milliseconds)	3,550	0	3,550
Superstep 2 (milliseconds)	17,905	0	17,905
Superstep 1 (milliseconds)	19,608	0	19,608


Jython:
Total (milliseconds)	244,965	0	244,965
Superstep 3 (milliseconds)	43,405	0	43,405
Setup (milliseconds)	3,735	0	3,735
Shutdown (milliseconds)	117	0	117
Superstep 0 (milliseconds)	36,962	0	36,962
Superstep 4 (milliseconds)	46,088	0	46,088
Input superstep (milliseconds)	8,551	0	8,551
Superstep 5 (milliseconds)	22,040	0	22,040
Superstep 2 (milliseconds)	42,329	0	42,329
Superstep 1 (milliseconds)	41,737	0	41,737


So the initial overhead of Jython vs Java is around 2.5x. I already see some additional improvements that can be made for example reading the Jython script only once as opposed to in each thread on each superstep as I do right now. I will work on this and look at other improvements as well.

Take a look at the reviewboard for latest patch: https://reviews.apache.org/r/11709/

  was:
Support for writing Computation code in other languages, e.g. Python. We add Jython bindings so that the Python computation code can communicate back with the Java Giraph classes.

https://reviews.apache.org/r/11709/

    
> Jython for Computation
> ----------------------
>
>                 Key: GIRAPH-683
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-683
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Nitay Joffe
>            Assignee: Nitay Joffe
>
> Support for writing Computation code in Python. We add Jython bindings so that the Python computation code can communicate back with the Java Giraph classes.
> To make this work I had to change a few parts of Giraph:
> 1) The Jython computation is not known until we read the script and create a Computation object for it at runtime. This has to be done on each worker separately after the job has launched. Because of this, there is no Computation class set at the beginning. I suspect other scripting languages will have similar issue. To fix this I created a ComputationFactory interface which is responsible for creating the Computation, with a default that just grabs the class from the Configuration and creates it.
> 2) I created a GiraphTypes class to hold the I,V,E,M1,M2 classes. There was a lot of repetitive code around these things so centralizing it all in one place made things a lot cleaner.
> 3) I added some more helpers like isDefaultValue() to our conf options.
> This patch contains our page rank benchmark implementation in Jython. I added an option (--jython) which chooses whether to run the default or the jython version.
> To use Jython all the user has to do is call Jython#init(...) somewhere in his initialization.
> Here is the initial comparison (4 workers, 10M vertices, 25 edges per vertex):
> Java:
> Total (milliseconds)	104,388	0	104,388
> Superstep 3 (milliseconds)	16,750	0	16,750
> Setup (milliseconds)	2,895	0	2,895
> Shutdown (milliseconds)	50	0	50
> Superstep 0 (milliseconds)	15,838	0	15,838
> Superstep 4 (milliseconds)	19,088	0	19,088
> Input superstep (milliseconds)	8,700	0	8,700
> Superstep 5 (milliseconds)	3,550	0	3,550
> Superstep 2 (milliseconds)	17,905	0	17,905
> Superstep 1 (milliseconds)	19,608	0	19,608
> Jython:
> Total (milliseconds)	244,965	0	244,965
> Superstep 3 (milliseconds)	43,405	0	43,405
> Setup (milliseconds)	3,735	0	3,735
> Shutdown (milliseconds)	117	0	117
> Superstep 0 (milliseconds)	36,962	0	36,962
> Superstep 4 (milliseconds)	46,088	0	46,088
> Input superstep (milliseconds)	8,551	0	8,551
> Superstep 5 (milliseconds)	22,040	0	22,040
> Superstep 2 (milliseconds)	42,329	0	42,329
> Superstep 1 (milliseconds)	41,737	0	41,737
> So the initial overhead of Jython vs Java is around 2.5x. I already see some additional improvements that can be made for example reading the Jython script only once as opposed to in each thread on each superstep as I do right now. I will work on this and look at other improvements as well.
> Take a look at the reviewboard for latest patch: https://reviews.apache.org/r/11709/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira