[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave Interpreter
From: |
Stefan Seefeld |
Subject: |
Re: Octave Interpreter |
Date: |
Sun, 05 Oct 2014 19:27:58 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 |
Hi Richard,
On 2014-10-05 13:29, Richard Crozier wrote:
>
>
> On 02/10/14 13:34, Stefan Seefeld wrote:
>> I'm honestly not entirely sure I understand the question: What
>> additional support in terms of language support is needed to provide a
>> "distributed Octave" ?
>
> Making 'parfor' loops work with actual parallel pools might be what is
> meant:
>
> http://www.mathworks.co.uk/help/distcomp/parfor.html
I see. Still, it seems the frontend (language) changes are only minimal,
while quite a lot needs to be done in terms of backend work to support this.
Could anyone familiar with the Octave internals comment on what it
would take to support parallel execution (in the sense of multiple
octave instances executing tasks dispatched from a single frontend
session (akin to the architecture described in
http://ipython.scipy.org/talks/0903_siamcse09_ipython_dist_bgranger.pdf,
slides 9-10) ? In other words, what does it take for Octave to support
MPI-style parallelism ?
Stefan
--
...ich hab' noch einen Koffer in Berlin...
- Octave Interpreter, Manu Kaul, 2014/10/01
- Re: Octave Interpreter, Bipin Mathew, 2014/10/02
- Re: Octave Interpreter, Stefan Seefeld, 2014/10/02
- Re: Octave Interpreter, Richard Crozier, 2014/10/05
- Re: Octave Interpreter,
Stefan Seefeld <=
- Re: Octave Interpreter, c., 2014/10/06
- Re: Octave Interpreter, Stefan Seefeld, 2014/10/06
- Re: Octave Interpreter, c., 2014/10/06
- Re: Octave Interpreter, Stefan Seefeld, 2014/10/06
- Re: Octave Interpreter, c., 2014/10/06
- Re: Octave Interpreter, Bipin Mathew, 2014/10/06
- Re: Octave Interpreter, Stefan Seefeld, 2014/10/06
- Message not available
- Re: Octave Interpreter, Stefan Seefeld, 2014/10/06