Intel® VTune™ Amplifier
Use this configuration to specify an Android application package to analyze with the Intel® VTune™ Amplifier for Systems via ADB connection.
To access the configuration, open the Analysis Target window, choose the Android (ADB) target system on the left, select the Launch Android Package target type from the drop-down menu on the right and in the via ADB on device drop-down menu select your Android device.
Make sure to prepare your target Android system for analysis:
Configure your Android device for analysis.
Gain adb access through TCP/IP to an Android device.
To enable hardware-event-based sampling analysis or Java* analysis, gain root mode adb access to the Android device.
Depending on your system configuration, you may not need to gain a root mode access for Advanced Hotspots, General Exploration and Custom EBS analysis types.
To enable hardware-event-based sampling analysis, verify that version compatible pre-installed signed drivers are on the target Android system.
|
Use This |
To Do This |
|---|---|
|
Package name field |
Specify the name of the Android package (*.apk) to analyze. To see a list of available packages, click the Browse button and select the required package in the Select Package dialog box. |
|
Automatically resume collection after (sec) |
Specify the time that should elapse before the data collection is resumed. When this options is used, the collection starts in the paused mode automatically. |
|
Automatically stop collection after (sec) |
Set the duration of data collection in seconds starting from the target run. This is useful if you want to exclude some post-processing activities from the analysis results. |
|
Managed code profiling mode menu |
Select a profiling mode for managed code. Managed mode attributes data to managed source and only collects managed portion. Native mode collects everything but does not attribute data to managed source. Mixed mode collects everything and attributes data to managed source where appropriate. |
Use the Advanced section to provide more details on your target configuration.
|
Use This |
To Do This |
|---|---|
|
Duration time estimate menu |
Estimate the application duration time. This value affects the size of collected data. For long running targets, sampling interval is increased to reduce the result size. For hardware event-based sampling analysis types, the VTune Amplifier uses this estimate to apply a multiplier to the configured sample after value. |
|
Analyze system-wide check box |
Enable analyzing all processes running on the system. When disabled, only the target process is analyzed. This option is applicable to hardware event-based sampling analysis types only. |
|
Collection data limit, MB spin box |
Limit the amount of the raw data to be collected. Use this option to start analyzing the beginning of the target execution when the amount of collected data is very large and takes long to process. Outcome: VTune Amplifier suspends data collection when the specified limit is reached.
NoteThe size of data stored in the result directory may not exactly match the specified limit due to the following reasons: |
|
Slow frames threshold, frames/s |
Specify a threshold to separate Slow and Good frames. Frame rates lower than this threshold are marked as Slow. This threshold needs to be smaller than the Fast frames threshold. |
|
Fast frames threshold, frames/s |
Specify a threshold to separate Good and Fast frames. Frame rates higher than this threshold are marked as Fast. This threshold needs to be larger than the Slow frames threshold. |
|
CPU mask |
Specify CPU(s) to collect data on (for example: 2-8,10,12-14). This option is applicable to hardware event-based analysis types only. |
|
Custom collector |
Provide a command line for launching an external collection tool, if any. You can later import the custom collection data (time intervals and counters) in a CSV format to a VTune Amplifier result. Click the Modify button to add a path to your external collector. |
|
Result location options |
Select where you want to store your result file. By default, the result is stored in the project directory. |