Hi, Dave,

Since 2.1.2, X10 comes with what we call a multi-vm Java backend
implementation.  It runs with the sockets transport.  For sockets, the
Java runner, "x10", uses the same launcher as the C++ backend
("X10Launcher"), so one can run it on, e.g., a Linux cluster by
setting X10_NPLACES and X10_HOSTFILE, just like you would for a C++
launch.

As far as I know, you cannot use the MPI transport with multi-vm.
        Igor

On Fri, Jun 24, 2011 at 4:47 PM, David E Hudak <dhu...@osc.edu> wrote:
> Hi All,
>
> I have a colleague with a Java implementation of a genetic algorithm.  He is 
> interested in parallelizing the application for both multicore and multinode 
> execution.
>
> In the initial implementation, there are a set of classes for specifying 
> fitness functions, expressing genes and implementing gene manipulations.  
> There is a top-level simulation object that run the various number of 
> generations.  My plan was to try using the java native interface to use the 
> existing Java classes for organisms and fitness, and rewrite the top level 
> simulation in X10.
>
> I have been evaluating X10 for purely numeric applications on our cluster 
> (C++ back end, MPI runtime and mpiexec as a process launcher).  I believe I 
> read somewhere that the Java native interface requires the Java back end.  In 
> that case, I'd need to make sure we could run the sockets runtime and 
> whatever process launcher we have for java (x10run?).
>
> Anyone have any advice?
>
> Thanks,
> Dave

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a 
definitive record of customers, application performance, security 
threats, fraudulent activity and more. Splunk takes this data and makes 
sense of it. Business sense. IT sense. Common sense.. 
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users

Reply via email to