Lines Matching refs:record
17 - [Record and report profiling data](#record-and-report-profiling-data)
18 - [Record and report call graph](#record-and-report-call-graph)
21 - [Record both on CPU time and off CPU time](#record-both-on-cpu-time-and-off-cpu-time)
35 - [The record command](#the-record-command)
36 - [Select events to record](#select-events-to-record)
37 - [Select target to record](#select-target-to-record)
38 - [Set the frequency to record](#set-the-frequency-to-record)
39 - [Decide how long to record](#decide-how-long-to-record)
41 - [Record call graphs](#record-call-graphs-in-record-cmd)
42 …- [Record both on CPU time and off CPU time](#record-both-on-cpu-time-and-off-cpu-time-in-record-c…
74 1. It collects more info in profiling data. Since the common workflow is "record on the device, and
95 simpleperf executables can be pushed on any Android device and used to record profiling data.
274 Normally we need to use the app when profiling, otherwise we may record no samples. But in this
280 Cmdline: /data/data/com.example.simpleperf.simpleperfexamplewithnative/simpleperf record ...
309 We can record and report [call graphs](#record-call-graphs-in-record-cmd) as below.
347 To show flame graphs, we need to first record call graphs. Flame graphs are shown by
368 We can [record both on CPU time and off CPU time](#record-both-on-cpu-time-and-off-cpu-time-in-reco…
459 Simpleperf has three main commands: stat, record and report.
467 The record command records samples of the profiled processes in a time period. Here’s how it works:
488 The record command: profiles processes and stores profiling data in perf.data.
502 # Print help message for record command.
503 $ simpleperf record --help
506 Below describes the most frequently used commands, which are list, stat, record and report.
684 ### The record command
686 The record command is used to dump samples of the profiled processes. Each sample can contain
696 $ simpleperf record -p 7394 --duration 10
700 #### Select events to record
707 $ simpleperf record -e instructions -p 11904 --duration 10
710 $ simpleperf record -e task-clock -p 11904 --duration 10
713 #### Select target to record
715 The way to select target in record command is similar to that in the stat command.
719 $ simpleperf record -p 11904,11905 --duration 10
722 $ simpleperf record -t 11904,11905 --duration 10
725 $ simpleperf record ls
729 $ simpleperf record --app com.example.simpleperf.simpleperfexamplewithnative
732 $ simpleperf record -a --duration 10
735 #### Set the frequency to record
741 means dumping one record whenever 10000 events happen.
745 $ simpleperf record -f 1000 -p 11904,11905 --duration 10
748 $ simpleperf record -c 100000 -t 11904,11905 --duration 10
758 $ simpleperf record -f 1000 -p 11904,11905 --duration 10 --cpu-percent 50
761 #### Decide how long to record
763 The way to decide how long to monitor in record command is similar to that in the stat command.
767 $ simpleperf record -p 11904 --duration 10
770 $ simpleperf record ls
773 $ simpleperf record -p 11904 --duration 10
787 $ simpleperf record -p 11904 -o data/perf2.data --duration 10
790 <a name="record-call-graphs-in-record-cmd"></a>
814 a function is called by other functions. To show a call graph, we need to first record it, then
817 There are two ways to record a call graph, one is recording a dwarf based call graph, the other is
824 $ simpleperf record -p 11904 -g --duration 10
827 $ simpleperf record -p 11904 --call-graph fp --duration 10
832 <a name="record-both-on-cpu-time-and-off-cpu-time-in-record-cmd"></a>
839 To support this, the record command uses --trace-offcpu to trace both on CPU time and off CPU time.
860 $ simpleperf record -g -p 11904 --duration 10 --trace-offcpu
868 First we record without --trace-offcpu.
893 The report command is used to report profiling data generated by the record command. The report
913 Cmdline: /data/data/com.example.sudogame/simpleperf record -p 7394 --duration 10
1001 as [here](#record-call-graphs-in-record-cmd).
1012 app_profiler.py is used to record profiling data for Android applications and native executables.
1034 # Record an Android application, and use -r to send custom options to the record command.
1049 the record command. The --app option sets the package name of the Android application to profile.
1050 If the app is not already running, the record command will poll for the app process in a loop with
1051 an interval of 1ms. So to profile from launch of an application, we can first start the record
1055 $ python run_simpleperf_on_device.py record
1094 when you record profiling data using `simpleperf record` directly, to do system wide profiling or
1095 record without the USB cable connected.
1225 record command. Internally, it uses libsimpleperf_report.so to do the work. Generally, for each
1229 (via GetCallChainOfCurrentSample). We can also get some global information, like record options
1290 The simpleperf record command collects symbols on device in perf.data. But if the native libraries