|
From: | David Grohmann |
Subject: | profiler and/or debugger, loops vs vectorization |
Date: | Fri, 30 Jun 2006 15:54:36 -0500 |
User-agent: | Thunderbird 1.5.0.4 (Windows/20060516) |
Is such a large performance hit likely caused by loops vs vectorization or might there be another explanation besides that?
I've searched online and haven't found anything to profile m files with, other than in matlab. I have profiled it in matlab and sure enough it does run the lines in the loops many (hundreds of thousands of times) times but only one of the loops actually takes up a lot of run time. This would probably be a good candidate for vectorizing. I suspect.
So is there anything out there for profiling or stepping through code in an m file in octave?
I know I haven't posted the offending code, that is because I currently don't have the authorization to do that. So my general question is how do people profile their code and what not. I'm not asking you to fix my code for me.
Thank you for any help you provide, -- David Grohmann Senior Student Associate Applied Research Lab : UT Austin : ESL - S206 Office: 512-835-3237
[Prev in Thread] | Current Thread | [Next in Thread] |