Instrumentation

The process of inserting extra diagnostic code during compilation of a given source code.

Profiling

Profiling is the process of measuring an application or system by running an analysis tool called a profiler



Time es code

Example

"The time profiling instrumentation isn t designed to profiling opengl es code;apple provides separate instrumentation for profiling opengl es code"

from question  

Finding all openGL calls in iOS instruments

"If you re writing a mac app the opengl profiling tool profiling opengl code better than instrumentation"

from question  

Instruments profiling: "top functions" reorders functions

Others

Example

This is due to the fact that profiling need to instrumentation the code to keep track of invocations - this can interfere with the jit s ability to inline those methods and the instrumentation overhead becomes significantly larger than the time spent actually executing the methods body

from question  

Performance in Java through code?

Enabling profiling does more profiling of your code but if your only goal is to get sql queries installing extension is all you need assuming instrumentation key is set correctly

from question  

Azure Application Insights for monitoring SQL Queries

I would definitely recommend using instrumentation to profiling what message is taking the most time so you can really break what message down

from question  

Merging two UIImages faster than CGContextDrawImage

A profiling will not be a solution to a coding style that is x slower than optimal however you still need to spend time fine-tuning those parts of your code that are used more often than others;because of instrumentation profiled code on average will run slower than non-profiled code

from question  

Java profiling - How reliable are the values it gives?

Paulw11 s comment helped--the time profiling template is better suited for this task than the system trace instrumentation

from question  

App freezes but CPU usage increases over time

As you noted tier interaction profiling tip gives you more detailed information about calls to databases right down to the sql statements for more information refer to the profiling blog;another recommended option when profiling asp.net is to profile using instrumentation mode

from question  

Using Visual Studio 2010 Profiler for ASP.NET web pages. Anything helpful besides 'tier interactions'? code coverage?

Knowing where inlining was really being done would give me a warm fuzzy feeling;but profiling seems more promising and useful generally;i fear the benefits are more intuitively real than actually and compiler writers are better off pursuing c++0x features run-time instrumentation introspection or writing d on the side

from question  

How do I find how C++ compiler implements something except inspecting emitted machine code?

This is useful for code profiling but not so much for memory profiling;build mono.cecil for the cf and use it to instrumentation emit right on the target device

from question  

Running a code profiler on Windows Mobile device

With the code you have here your instrumentation is much much more expensive than the work being done which makes the profiling data useless

from question  

Global values inside template function not changing [c++]

So my question is beyond instrumentation and the profiling using memory leaks which tells you the location of creation of the leaky object but not the root cause are there any other tools i could run that could give me any more info than instrumentation re tracking down the root cause point

from question  

Re Instruments 'Memory Leak' profiling, do other tools give any more info re finding root cause of a leak?

Back to Home
Data comes from Stack Exchange with CC-BY-SA-4.0