[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave Interpreter
From: |
c. |
Subject: |
Re: Octave Interpreter |
Date: |
Mon, 6 Oct 2014 14:28:09 +0200 |
On 6 Oct 2014, at 14:07, Stefan Seefeld <address@hidden> wrote:
> Right. I think pure data parallelism as done with MPI isn't very
> practical for an interpreter, as lots of commands typed interactively
> aren't meant to be executed in parallel. On the other hand, spawning
> other processes for a single parallel operation may not be practical
> either. Perhaps something like a thread-pool pattern would work, where
> processes are spawned upfront, but are kept in stand-by mode until a
> parallel region is entered where data (and computation) is allocated to
> them.
I have been interested in this project myself,
what I thought of is something like:
[out1, out2] = mpirun (numproc, function, input1, input2, ...)
to run an MPI based Octave function from the Octave prompt.
Would that suit you as well?
> Stefan
c.
- 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, 2014/10/05
- Re: Octave Interpreter, c., 2014/10/06
- Re: Octave Interpreter, Stefan Seefeld, 2014/10/06
- Re: Octave Interpreter,
c. <=
- 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