Path: news.mathworks.com!not-for-mail
From: "Charles Cuell" <cuell@math.usask.ca>
Newsgroups: comp.soft-sys.matlab
Subject: Re: much faster MATLAB
Date: Tue, 7 Oct 2008 21:28:01 +0000 (UTC)
Organization: Environment Canada
Lines: 18
Message-ID: <gcgk91$n7s$1@fred.mathworks.com>
References: <gcebi7$otk$1@fred.mathworks.com>
Reply-To: "Charles Cuell" <cuell@math.usask.ca>
NNTP-Posting-Host: webapp-02-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1223414881 23804 172.30.248.37 (7 Oct 2008 21:28:01 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Tue, 7 Oct 2008 21:28:01 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 811838
Xref: news.mathworks.com comp.soft-sys.matlab:494148


"Kevin Johnson" <defer.jof@gmail.com> wrote in message <gcebi7$otk$1@fred.mathworks.com>...
> All,
> 
> I have been using MATLAB for many years now but finally its speed has become a major limiting factor.  As time has gone on, large segments of my code are no longer in need of further development (though other segments are). These same segments are the ones that consume most of the computation time. 
> 
> Mex files are the solution I suppose; however the last time I programmed in Fortran was 30 years ago, and in C, never. In reading about mex files, it sounds daunting for a basically amateur (in terms of skills) programmer like me. 
> 
> In a broad sense, what would be the best approach to substantially (at least 10x) speed up these unchanging swaths of code, for someone who is not a programmer?  I'd be able to invest in a solution within reason.
> 
> Thanks


Also, consider the possibility that writing, debugging, testing, debugging, optimizing, debugging, and running C++ code may actually take longer than just waiting for the Matlab code to run.

If I knew then what I know now, I wouldn't know anything about C++ and I'd be a year younger.

Charles
>