| Re: IDL profiler [message #72687 is a reply to message #72607] |
Mon, 27 September 2010 11:45   |
chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
|
Senior Member |
|
|
On Sep 27, 12:05 am, Mrunmayee <gaur...@gmail.com> wrote:
>> I presume the rest of the time is spent in system
>> routines that aren't listed in the profile, but
>> I really don't know. Nor can I get myself to
>> care too much about it, if you know what I mean. :-)
>
>> Why are you treating this information in such
>> an absolute way? If you are looking for places
>> where your code is slow, Profile will show you
>> that. Why care what the absolute time is?
>
>> Cheers,
>
>> David
>
>> --
>> David Fanning, Ph.D.
>> Fanning Software Consulting, Inc.
>> Coyote's Guide to IDL Programming:http://www.dfanning.com/
>> Sepore ma de ni thui. ("Perhaps thou speakest truth.")
>
> I just wanted to make sure I understand what's going on inside the
> profiler's belly. I did use the info to identify the part of the code
> that was taking up time. As for system routine, I had issued commands
> 'profiler,/system & profiler' to profile both -user-defined and system
> routines. So it showed time spent in my routines as well as routines
> such as sin, cos, rebin etc. And my confusion was, even then it
> doesn't add up to total time.
>
> Not worrying, though. Just trying to get a clearer picture.
Have you tried the "Profiler View" in the IDL Workbench? It will give
you a graphical display of the profiler results, with a table of the
different times. You can then sort on each column, and export the
results to a text file, etc.
Just a suggestion.
-Chris
ITTVIS
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
