In profiling software, why is percentage used instead of time in milliseconds?

My colleague and I looked at the Visual Studio profiling report in VS2012, and they asked me: “Why do you use percentages to express the length of time in a method or the time spent invoking a method?”

My explanation was that the tool provides some insight into which methods / calls take a lot of time or which parts of a method take a lot of time. Now it can be an abstraction (percentage) or something absolute (time (ms)), but this is enough to indicate problem areas in your application.

We were not particularly convinced of this, so I thought that I would ask the Internet.

+5
source share
5 answers

This is Andre Hamilton from the Visual Studio Profiler team. The reason the values ​​are shown in percentages rather than ms is because you are seeing a report based on Profiler profiling, not Instrumentation.

Profiling Samples Basically, the operating system will periodically execute the stack. The results that you see in the profiling report are part of the time that the OS ran the stack, that a specific function was on the stack

( ) . , . , . enter & exit, ( 1 ). , , . . , . , - , .

FYI Visual Studio vsinstr ( \Team Tools\Performance Tools).

+7

, .

: , , , . , , , , .

. , , , . , , - , .

, , , ( , , ).

+2

?

  • , powerpoint? ...

  • , ? ( .)

(2), , : a) , b) . , , X (, 50%) , , , 1/(1-X) .

"", . , " ", , , .

, . . , , . , , 50%, 25% 12,5%, , 8 . . , , .

-, , ? , , , , , , ? . .

+2

: 32 , 1 .

, ( 1), - ", ", , , .

1 , .

+1

The percentage is good. But you need to have time in milliseconds. If you need to compare two versions of software that perform the same task, one takes much longer than the other. Interest is harder to compare than the absolute time spent on each function. Why not give us the opportunity to see the percentages of absolute time?

I am very surprised that this was no longer raised.

0
source

All Articles