Home/ Questions/Q 6060077
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T08:47:03+00:00

I just don’t get the various elements of the traceview output, and I can’t

  • 0

I just don’t get the various elements of the traceview output, and I can’t find a tutorial. Could someone please explain the following with reference to the diagram below:

enter image description here

  1. The width of the bars corresponds to the time the function takes. What does the height correspond to?
  2. What is specific difference between Inclusive and Exclusive. I assumed that inclusive includes the calls of all the children functions?
  3. Would this be true: The sum of (Time per call times Calls) = time the program runs (what about async tasks?)
  4. Can async tasks be ignored when debugging slowdown on the main thread ?
  5. Should the sum of all the percents in Excl% equal 100%?
  6. What happens when there are gaps (white in the midst of black)? Is that when other android processes are running, or just your own async tasks (it looks like the gaps in one are aligned with the filled in part in the other, if thats the case then is there any point in moving intensive tasks to an AsyncTask)?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I cant answer all your questions, but I can say…

    for #4 no, You’re running a single core processor (or at least emulating one) so async tasks on their own thread have to interrupt main thread to get processing time. Any time another thread executes will be “slowdown” on the main thread, so you should be watching that.

    for #6, those gaps you see in your main threads execution trace correlate exactly to the times when your asynctask is getting processor time. Again, single core, can only do 1 thread at a time. In this time slice it doesnt look like any other process got any processor time at all, but those threads were still sleeping in the background. Since this was (likely) an emulator, thats common. On a live phone you will see many more 🙂

    I’m also fairly sure for #1 that the height of each spike in the thread’s execution is the %processor utilization. For example the main thread’s “black” area is system idle. Edit: Ok, i’m for sure now. This is what that is. So in your main thread, that area that is solid pink is solid 100% processor utilization.

    • 0