2) Press the blue Connect button.
3) Set the Session Type to Local.
4) Fill in Application Settings with its path, arguments, working directory, and bitness.
5) Press Next, followed by Connect, which should start-up GPUPerfServer plus the Vulkan application.
6) An API selection dialog will appear, which will list the Vulkan application if it is running. Select it and press OK.
7) Press either the API Trace, GPU Trace, or Linked Trace button to begin analysis.
2) At this point, the application should be running alongside an active GPUPerfServer terminal window.
3) Launch GPUPerfClient.exe.
4) Press the blue Connect button.
5) An API selection dialog appear, which will list the Vulkan application if it is running. Select it and press OK.
6) Press either the API Trace, GPU Trace, or Linked Trace button to begin analysis.
2) Remote machine: At this point, the application should be running alongside an active GPUPerfServer terminal window.
3) Local machine: Launch GPUPerfClient.exe.
4) Local machine: Press the blue Connect button.
5) Local machine: Set the Session Type to Remote, specify server IP, and specify port (default 8080)
6) Local machine: Press Next, followed by Connect, and an API selection dialog should appear with the Vulkan application listed. Select it and press OK.
7) Local machine: At this point, the client-server connection is established and the application may now be analyzed.
8) Local machine: Press either the API Trace, GPU Trace, or Linked Trace button to begin analysis.
Run the application on its own at least once, prior to running it through GPU PerfStudio.
Repeated experimentation is encouraged.
Users are not limited to one set of data per session. Users may refresh current data by repeatedly pressing the API Trace, GPU Trace, or Linked Trace buttons on the toolbar.
The default behavior is to show information for a single frame, but GPU PerfStudio has the ability to collect data across N frames. This number can be specified in the Settings pane, under Number of Frames to Capture.