[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Differences in Matlab/Octave processing time
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Re: Differences in Matlab/Octave processing time |
Date: |
Fri, 30 May 2008 11:50:19 -0500 |
On 29/05/2008, HempyElmo <address@hidden> wrote:
> With Octave on the same computer, it took ages...
[snip]
> I don't know how many loops it makes.
I think I've spotted your problem.
Octave doesn't have JIT like Matlab. This means that unvectorised code
in Octave suffers much more than it does in Matlab, by orders of
magnitude. The only fixes are (1) implement JIT in Octave, a proposal
that comes up once in a while, and I think right now some people are
actually trying to do that, but overall it seems to be too hard for
too little dividends or (2) write better (more vectorised) code.
I suggest you take approach (2).
- Jordi G. H.
- Differences in Matlab/Octave processing time, HempyElmo, 2008/05/29
- Re: Differences in Matlab/Octave processing time, Stuart Brorson, 2008/05/30
- Re: Differences in Matlab/Octave processing time, Francesco Potorti`, 2008/05/30
- Re: Differences in Matlab/Octave processing time, Michael Goffioul, 2008/05/30
- Re: Differences in Matlab/Octave processing time, David Bateman, 2008/05/30
- Re: Differences in Matlab/Octave processing time, Dmitri A. Sergatskov, 2008/05/30
- Re: Differences in Matlab/Octave processing time, Jaroslav Hajek, 2008/05/30
- Re: Differences in Matlab/Octave processing time,
Jordi Gutiérrez Hermoso <=
- Re: Differences in Matlab/Octave processing time, HempyElmo, 2008/05/30