Never ship an app without running it through Instruments first! Part3

Never ship an app without running it through Instruments first! Part3

Welcome back, Ready to start the Time Profiler, OK, but before starting be sure you have read the first two parts(part1, part2), and don't worry I'm waiting here!

After you have chosen Time Profiler from Instruments as the first tool we will discuss, let's start to analyze the window that appears so we can smoothly read it.

control stop/Running and pause the display

Recording Control: to start/stop or Pause the execution of the application.

No alt text provided for this image



Run timer: This shows(the number of Runs | the amount of time the profiled app has been running).

No alt text provided for this image



Instrument track: this is the place where instruments track your app from the perspective of which tool you have chosen, here we chose Time Profiler so it will read the change of time during app recording, don't worry if you do not fully understand, we will declare this again soon.

No alt text provided for this image





Detail Panel: details panel convert the graph that appears at the instrument track to its corresponding readings for each thread and function.

These displayed details will give very important information on the weight of each thread and each function(the ones that have used up the most CPU time).

Notice the call tree at the bottom it will give us readings from different perspectives to facilitate understanding those details.

No alt text provided for this image








Inspectors panel: There are two inspectors —?Extended Detail?and?Run Info?— we will know how to use them shortely.

Do you feel that you are a bit familiar with the Time Profiler window? it will be more clearer in the next article, so don't be late.


要查看或添加评论,请登录

Eman Shedeed的更多文章

社区洞察

其他会员也浏览了