Re: Profiling and inlining
- From: ti@xxxxxxxxxxx
- Date: 20 Jul 2006 17:24:44 -0700
Thanks for the advice. I didn't realize that instrumentation was
unreliable for timing. I'll proceed with the sampling in VSTE.
In that context, do you know of a good way to get a brakedown of which
statements in a big function are the time consuming ones? The Profiler
in VSTE will only tell me the time for the function itself.
Barry Kelly wrote:
ti@xxxxxxxxxxx wrote:
I've done both. Though mostly instrumetation-based, since I was
interested in measures for which specific lines in a few big functions
were most costly.
Instrumentation can't reliably monitor time performance, since it
changes the code. For example, it typically prevents inlining. Usually,
a sampling profiler is needed, unless you're trying to track down a
problem that shows a method is being called more often than you think it
should be.
Quantify does this easily, and I don't think VS
2005's profiler does it.
VS 2005 Team Edition (I last looked in Beta 2, I only have Pro) appears
to have two profilers, one for instrumentation (best for memory
profiling) and another for sampling (best for time profiling).
-- Barry
--
http://barrkel.blogspot.com/
.
- Follow-Ups:
- Re: Profiling and inlining
- From: Barry Kelly
- Re: Profiling and inlining
- References:
- Profiling and inlining
- From: ti
- Re: Profiling and inlining
- From: Barry Kelly
- Re: Profiling and inlining
- From: ti
- Re: Profiling and inlining
- From: Barry Kelly
- Profiling and inlining
- Prev by Date: Re: Profiling and inlining
- Next by Date: Re: Profiling and inlining
- Previous by thread: Re: Profiling and inlining
- Next by thread: Re: Profiling and inlining
- Index(es):
Relevant Pages
|