System Analyzer Getting Started Guide

Introduction

In general, System Analyzer provides real-time platform & app analysis capability*. With this utility, developers can easily check the real-time changes on the performance metrics they care (e.g. CPU/GPU loading, media engines usage and power metrics etc.) while interacting with their target test app.

 

Take the first look about System Analyzer below. Metrics names listed in left panel can be dragged-and-dropped into right view panels for real-time monitoring.

 

*For the further advanced topics, System Analyzer is part of GPA (Graphics Performance Analyzer) which focuses more on graphics app optimization usage, mainly on Windows DirectX app and Android OpenGL ES app. Check the GPA product page to get the quick overview of GPA.

System Analyzer can be ran on Windows/Linux/Mac host to analyze Android and Windows applications. The support matrix is listed below.

Host(Developer machine)\Target

Android

Windows

Windows

Remote mode

Local mode

Linux

Remote mode

N/A

Mac

Remote mode

N/A

* Remote mode – requires ADB connection.
* Local mode – System Analyzer and test app run on the same machine.

The next section gives a quick start about how local mode works. Before that, System Analyzer is contained in both professional and ultimate editions of Intel® System Studio 2015 (It's also in Intel® INDE). You can download these binaries via registering the Intel System Studio products or downloading the free version from INDE.

A quick start for local mode (profile a window application)

After installed GPA System Analyzer through Intel System Studio Professional or Ultimate editions, you can perform the following steps to see how System Analyzer works to profile a windows application.

  1. Make sure GPA System Analyzer are installed on the system.
     
  2. Launch the Graphics Monitor. (Shown as an Tray Icon on the taskbar)
     
  3. Right click the Tray Icon of Graphics Monitor to show context menu, select Analyze Application then run your test app
     
  4. Launch the System Analyzer, select <This Machine> or localhost then click Connect.
     
  5. Attach the process by selecting your test app from the list

A usage case: is your application GPU-bound?

If your application is CPU-bound, that could say CPU is the critical resource to limit your application performance, in other words, you should be able to gain better performance after simply adopting higher working CPU frequency processor (or make CPU run faster). Knowing which resource bounds the program’s performance is a good direction to show you how to fine-tune your codes; optimize the codes path consuming most CPU computation resource if your program is CPU-bound type. It’s the same concept for GPU-bound program.

System Analyzer simply provides a switch to test if your program is GPU-bound or not. (To be more specific, 3D-Rendering-engine-bound or not)

Make sure you successfully perform a quick start above. By clicking “Null Hardware” option, you could assume to have an infinite fast 3D hardware engine. Then you shall expect the maximum best performance measurement index (like highest FPS) shows in right panel view if the test program is 3D-Rendering-engine-bound.

There are many test options (STATE OVERRIDES) to help isolate which rendering state causing performance bottle neck. Through these tests, you should be able to find the direction or focus points to improve the graphics program. Check the help page for more information on these state overrides options.

Further information

Intel System Studio includes three components of GPA; they are System Analyzer, Platform Analyzer and Frame Analyzer. System Analyzer is also the central interface to record the logs what Platform Analyzer and Frame Analyzer used for offline analysis.

GPA Analyzers NameFunctionalities
System AnalyzerProvide real-time system & app analysis. The central interface to record/capture logs for other GPA analyzers. More information.
Platform AnalyzerProvide GPU engines and threads activities interactions analysis. Present the captured log by showing all graphics hardware engines workloads (including decoding, video processing, rendering and computing) and threads activities in a timeline view. More information.
Frame AnalyzerProvide a offline single frame rendering analysis. Reconstruct the frame by replaying DirectX/OpenGL APIs logged by System Analyzer. More information

See also

For more complete information about compiler optimizations, see our Optimization Notice.