Lines Matching refs:samples

46         - [Filter samples](#filter-samples)
47         - [Group samples into sample entries](#group-samples-into-sample-entries)
75    report on the host", simpleperf not only collects samples in profiling data, but also collects
274 Normally we need to use the app when profiling, otherwise we may record no samples. But in this
467 The record command records samples of the profiled processes in a time period. Here’s how it works:
472 5. Simpleperf reads samples from the mapped buffers and stores profiling data in a file called
686 The record command is used to dump samples of the profiled processes. Each sample can contain
691 what frequency to dump samples, how long to monitor, and where to store samples.
695 # frequency (4000 samples per second), writing records to perf.data.
751 To avoid taking too much time generating samples, kernel >= 3.10 sets the max percent of cpu time
752 used for generating samples (default is 25%), and decreases the max allowed sample frequency when
835 Simpleperf is a CPU profiler, it generates samples for a thread only when it is running on a CPU.
895 groups samples belong to the same process, thread, library, function in the same sample entry. Then
898 By passing options, we can decide how to filter out uninteresting samples, how to group samples
956 #### Filter samples
959 filters to select samples of interest.
975 #### Group samples into sample entries
1227 Then we can read all samples through GetNextSample(). For each sample, we can read its event info
1259    to be 1000 Hz. Thus at most 1000 samples per second.