Threads: Displays a list of threads and their utilization data in the timeline pane.The instruments list is visible by default when you create a trace document. If you select an instrument in the list, you can delete it or configure it in the inspector pane. Instruments: Displays a list of instruments and their corresponding data in the timeline pane.Only available when a trace document contains instruments that record CPU data. CPUs: Displays a list of CPU cores, along with their usage over time, in the timeline pane.Click the strategy buttons in the filter bar to display instruments, CPU core, thread data, or all three items in the timeline.This pane’s information is read-only, you can scroll through data, select specific areas for closer examination, and insert flags to highlight points of interest.Timeline pane: Displays a graphical summary of the data recorded for a given trace.View buttons (): Hide or show the detail pane and inspector.From here, you can select individual instruments and add them to your trace document. Add Instrument button (+): Shows or hides the instruments Library palette, which contains a complete list of available instruments.Activity viewer: Shows the number of runs for the trace document and the elapsed time of the current trace.Target process list: Allows you to select the process or processes to profile.Target device list: Allows you to select the device on which you wish to profile.Profiling controls: Allow you to record, pause, and stop data collection.Toolbar: Allows you to start, pause, and stop data profiling, add instruments, hide and show panes, and more.The trace document includes the following main areas: In the profiling template selection dialog that appears, select a target device and find your app in the Running Applications list.Ĭlick the Record button in the toolbar (or press Command-R) to begin recording.Ĭlick the Stop button, or press Command-R again, when complete.Ī trace document is used to organize and configure instruments for profiling, initiate data collection, and view and analyze the results. In Xcode, choose Xcode > Open Developer Tool > Instruments. How to setup everything is explained below on example of non-debug build.Ĭonnect an iPhone with Macbook and open the app you want to profile (this is important because it won't work if the app is closed). The other option is good if you only need to check overall app performance without digging deep into the data. There is another option with using any build which doesn't require a developer but has a constraint which is hidden names for all collected data.

To start using Instruments and profile the app, an iOS developer will need to install a debug build on your device (preferable). To install Xcode, go to App Store and install it from there. If you are testing with the Instruments app and notice that the battery is draining fast, too much CPU is being used, etc., take a screenshot of the profiler and attach it to your task because this will help developers to find the issue much faster.Īlthough it's embedded within and may be used with Xcode, Instruments is a separate app, which may be used independently as needed. The Instruments app in Xcode provides a rich set of tools and templates for profiling your app performance that can help you debug and overcome performance issues, like bad CPU usage, poor implementation of battery resources, unnecessary memory consumption, etc. If you go out and you buy the most expensive frying pan on the market it's still not going to make you a good chef. Just like with everything else, tools won't give you good results unless you know how, when, and why to apply them.

Xcode instruments cpu profiler