Multiple Event-Based Sampling

The VTune(TM) Performance Analyzer runs the sampling collector to collect data based on selected events during event-based sampling (EBS).

Note that multiple events are automatically selected when an event group or an event ratio is selected.

If multiple events are selected, the sampling collector collects data based on two or more events during the same run. The number of events it can monitor during a single run is based on the processor installed in your system. See Performance counters on Intel(R) processors.

The VTune analyzer runs the sampling data collector as many times as required to collect data on all the events you specified.

In each run, if calibration is enabled, the sampling collector calibrates the Sample After value and then collects data for the selected events using the calibrated Sample After value. If the calibration is not enabled (it is enabled by default for some events), the VTune analyzer uses the default Sample After value and collects data on the selected events after every 5000 occurrences of the event.  

If you specified an application to launch when configuring the sampling collector, the VTune analyzer launches your application each time the sampling collector runs. If you enabled the Terminate application(s) when data collection finishes option in the General tab (-term-activity-end or -term option in the command-line interface) while configuring the sampling collector (it is enabled by default), the VTune analyzer terminates and re-launches your application automatically between each run.

note

After each run, as the VTune analyzer finishes data collection, an Activity result is generated and displayed in the Tuning Browser window.

When all the samples have been collected, the VTune analyzer displays the results in the default sampling view.
If you work from the command line, type in vtl showto view the project content and make sure the Activity result is generated. To view the collected data in the default sampling view, enter vtl view <ActivityName::ActivityResultName>.