Lines Matching full:trace
14 <li><a href="#limit-trace">Limiting trace data</a></li>
15 <li><a href="#config-categories">Configuring trace data categories</a></li>
16 <li><a href="#running">Running a trace</a></li>
66 <p>In order to create a trace of your application, you must perform a few setup steps. First, you
69 system and install your application. Some types of trace information, specifically disk activity
74 <h3 id="limit-trace">Limiting trace data</h3>
81 <li>Limit the amount of time covered by the trace with the {@code -t, --time} option. The default
82 length of a trace is 5 seconds.</li>
83 <li>Limit the size of the data collected by the trace with the {@code -b, --buf-size} option.</li>
89 <h3 id="config-categories">Configuring trace data categories</h3>
91 <p>To use {@code systrace} effectively, you must specify the types of processes you want to trace.
95 <li>General system processes such as graphics, audio and input processes (selected using trace
101 <p>To set trace tags for {@code systrace} using the command-line:</p>
116 <p>To set trace tags for {@code systrace} using the device user interface:</p>
126 selecting trace tags using this method.
130 <h3 id="running">Running a trace</h3>
132 <p>After you have configured the category tags for your trace, you can start collecting
135 <p>To run a trace using the current trace tag settings:</p>
140 <li>Run the trace with the low-level system trace options and limits you want, for example:
145 <li>On the device, execute any user actions you want be included in the trace.</li>
151 <p>After you have generated a trace using {@code systrace}, it lists the location of the output
153 How you use the trace data depends on the performance issues you are investigating. However,
154 this section provides some general instructions on how to analyze a trace.</p>
173 <strong>Figure 2.</strong> Excerpt from a trace of a smoothly running application with a regular
177 <p>The trace excerpt in figure 2 shows a well-behaved application with
179 the trace indicated by the dotted outline, which reveals some irregularity in the process
185 <p>Long running processes show up as thicker than usual execution bars in a trace. These thicker
187 trace, zoom in on the process using the
210 <strong>Figure 3.</strong> Excerpt from a trace of an application showing interruptions in
214 <p>The trace excerpt in figure 3 shows an section of a trace that indicates an interruption in the
218 area in the lower trace, shows that a memory operation (image buffer dequeuing and allocation) in
