comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » profiler

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Profiler [message #27420 is a reply to message #27333]

Fri, 19 October 2001 13:11

K. Bowman
Messages: 330
Registered: May 2000

Senior Member

In article <9qoeu3$hm8$1@mwrns.noaa.gov>, Pavel Romashkin
<pavel.romashkin@noaa.gov> wrote:

> Its been a while, nobody answered. Have you tried it, Ken?
> I only profiled perfectly debugged code (yeah, right) in order to optimize
> it. I never felt the need to profile line by line, it was obvious from the
> profile which part of the code was casuing the drag.

We have not figured out how to profile line-by-line. Doesn't seem to
be possible Turning on all the system routines, etc. didn't help
either for this problem.

We have resorted to the simple expedient of commenting out blocks of
code (where it won't affect the computation) or moving blocks of code
into temporary subroutines. In our case, at least, it has turned out
to be relatively simple to isolate the computationally-intensive block.

We have discovered a couple of minor algorithmic optimizations that we
are testing.

Ken

Report message to a moderator

[Message index]

		profiler By: J.D. Smith on Thu, 29 October 1998 00:00
		Re: Profiler By: Pavel A. Romashkin on Thu, 18 October 2001 22:50
		Re: Profiler By: K. Bowman on Fri, 19 October 2001 13:11
		Re: Profiler By: K. Bowman on Mon, 22 October 2001 11:37
		Re: Profiler By: Paul Woodford on Sat, 20 October 2001 20:01
		Re: Profiler By: Pavel A. Romashkin on Fri, 19 October 2001 14:23

Previous Topic:	Really really long format keywords
Next Topic:	Re: using an unlnown number of keywords

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 20:10:53 PDT 2025

Total time taken to generate the page: 0.00393 seconds