[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: speed comparison of IDL, numPy, Matlab
- Subject: Re: speed comparison of IDL, numPy, Matlab
- From: "Mark Hadfield" <m.hadfield(at)niwa.cri.nz>
- Date: Wed, 7 Feb 2001 12:10:55 +1300
- Cache-Post-Path: clam-ext!unknown@gust.greta.niwa.cri.nz
- Newsgroups: comp.soft-sys.matlab,comp.lang.python,comp.lang.idl-pvwave
- Organization: NIWA
- References: <3A7EEE5C.6419B707@pacific.jpl.nasa.gov>
- Xref: news.doit.wisc.edu comp.soft-sys.matlab:84089 comp.lang.python:122645 comp.lang.idl-pvwave:23405
"Benyang Tang" <btang@pacific.jpl.nasa.gov> wrote in message
3A7EEE5C.6419B707@pacific.jpl.nasa.gov">news:3A7EEE5C.6419B707@pacific.jpl.nasa.gov...
>
> Out of curiosity, I did a quick benchmark test of IDL, NumPy and Matlab on
my
> desktop machine. I know benchmarking is a complicated issue; don't take my
> naive test too serious.
I don't take it seriously at all, because you've only exercised a tiny
fraction of the code in each product.
As another very small contribution to the IDL vs NumPy vs Matlab discussion,
may I offer my observation that, when you are forced to write (quelle
horreur!) a for loop, IDL will process that loop significantly faster than
Matlab and orders of magnitude faster than Python. (I'm afraid I can't offer
the numbers to back up that assertion right now--it's based on comparisons I
did some time ago.)
Speaking as a long-time IDL user who has dabbled with Matlab & Python/NumPy,
I'd love to switch to NumPy, and I'd do it tomorrow if the graphics
capabilities were there.
---
Mark Hadfield
m.hadfield@niwa.cri.nz http://katipo.niwa.cri.nz/~hadfield/
National Institute for Water and Atmospheric Research
PO Box 14-901, Wellington, New Zealand