You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/install-guides/windows-perf-vs-extension.md
+22-28Lines changed: 22 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,38 +28,33 @@ multi_install: FALSE # Set to true if first page of multi-page article, else fal
28
28
multitool_install_part: false # Set to true if a sub-page of a multi-page article, else false
29
29
layout: installtoolsall # DO NOT MODIFY. Always true for tool install articles
30
30
---
31
+
[WindowsPerf](/install-guides/wperf/) is a lightweight performance profiling tool inspired by Linux Perf, and specifically tailored for Windows on Arm. It leverages the AArch64 Performance Monitoring Unit (PMU) and its hardware counters to offer precise profiling capabilities.
31
32
32
-
## Introduction
33
+
Recognizing the complexities of command-line interaction, the WindowsPerf GUI is a Visual Studio 2022 extension created to provide a more intuitive, integrated experience within the Integrated Development Environment (IDE). This tool enables developers to interact with WindowsPerf, adjust settings, and visualize performance data seamlessly in Visual Studio.
33
34
34
-
WindowsPerf is a lightweight performance profiling tool inspired by Linux Perf, and specifically tailored for Windows on Arm. It leverages the ARM64 PMU (Performance Monitor Unit) and its hardware counters to offer precise profiling capabilities.
35
-
36
-
Recognizing the complexities of command-line interaction, the WindowsPerf GUI is a Visual Studio 2022 extension created to provide a more intuitive, integrated experience within the integrated development environment (IDE). This tool enables developers to interact with WindowsPerf, adjust settings, and visualize performance data seamlessly in Visual Studio.
37
-
38
-
## A Glimpse of the available features
35
+
## Overview of key features
39
36
40
37
The WindowsPerf GUI extension is composed of several key features, each designed to streamline the user experience:
41
38
42
-
-**WindowsPerf Configuration**: Connect directly to `wperf.exe` for a seamless integration. Configuration is accessible via `Tools -> Options -> Windows Perf -> WindowsPerf Path`.
43
-
-**Host Data**: Understand your environment with `Tools -> WindowsPerf Host Data`, offering insights into tests run by WindowsPerf.
44
-
-**Output Logging**: All commands executed through the GUI are logged, ensuring transparency and aiding in performance analysis.
45
-
-**Sampling UI**: Customize your sampling experience by selecting events, setting frequency and duration, choosing programs for sampling, and comprehensively analyzing results.
39
+
-**WindowsPerf Configuration**: Connect directly to `wperf.exe` for a seamless integration. Configuration is accessible by selecting **Tools > Options > Windows Perf > WindowsPerf Path**.
40
+
-**Host Data**: Understand your environment by selecting **Tools** then **WindowsPerf Host Data**. This offers insights into tests run by WindowsPerf.
41
+
-**Output Logging**: All commands executed through the GUI are logged, ensuring transparency and supporting performance analysis.
42
+
-**Sampling UI**: Customize your sampling experience by selecting events, setting frequency and duration, choosing programs for sampling, and comprehensively analyzing results. See screenshot below.
-**Counting Settings UI**: Build a `wperf stat` command from scratch using the configuration interface, then view the output in the IDE or open it with Windows Performance Analyzer (WPA)
-**Counting Settings UI**: Build a `wperf stat` command from scratch using the configuration interface, then view the output in the IDE or open it with Windows Performance Analyzer (WPA). See screenshot below.
-**Visual Studio 2022**: Ensure you have Visual Studio 2022 installed on your Windows on Arm device.
61
-
-**WindowsPerf**: Download and install WindowsPerf by following the [WindowsPerf install guide](/install-guides/wperf/).
62
-
-**LLVM** (Recommended): You can install the LLVM toolchain by following the [LLVM toolchain for Windows on Arm install guide](/install-guides/llvm-woa).
54
+
Before installing WindowsPerf Visual Studio Extension, check the following:
55
+
1. Ensure Visual Studio 2022 is installed on your Windows on Arm device.
56
+
2. Download and install WindowsPerf by following the [WindowsPerf install guide](/install-guides/wperf/).
57
+
3. (Recommended) You can install the LLVM toolchain by following the [LLVM toolchain for Windows on Arm install guide](/install-guides/llvm-woa).
63
58
64
59
{{% notice llvm-objdump %}}
65
60
The disassembly feature needs to have `llvm-objdump` available at `%PATH%` to work properly.
@@ -69,11 +64,10 @@ The disassembly feature needs to have `llvm-objdump` available at `%PATH%` to wo
69
64
70
65
To install the WindowsPerf Visual Studio Extension from Visual Studio:
71
66
72
-
1. Open Visual Studio 2022
73
-
2. Go to the `Extensions` menu
74
-
3. Select **Manage Extensions**
75
-
4. Click on the search bar ( or tap `Ctrl` + `L` ) and type `WindowsPerf`
76
-
5. Click on the install button and restart Visual Studio
67
+
1. Open Visual Studio 2022.
68
+
2. Go to the **Extensions** menu and select **Manage Extensions**.
69
+
4. Click on the search bar (Ctrl+L) and type `WindowsPerf`.
70
+
5. Click on the **Install** button and restart Visual Studio.
@@ -83,7 +77,7 @@ You can also install the WindowsPerf Visual Studio Extension from GitHub.
83
77
84
78
Download the installation file directly from the [GitHub release page](https://github.com/arm-developer-tools/windowsperf-vs-extension/releases).
85
79
86
-
Unzip the downloaded file and double click on the `WindowsPerfGUI.vsix` file
80
+
Unzip the downloaded file and double click on the `WindowsPerfGUI.vsix` file.
87
81
88
82
{{% notice Note %}}
89
83
Make sure that any previous version of the extension is uninstalled and that Visual Studio is closed before installing the extension.
@@ -97,10 +91,10 @@ Building the source is not required, but offered as an alternative installation
97
91
98
92
### WindowsPerf Setup
99
93
100
-
To get started, you must link the GUI with the executable file `wperf.exe` by navigating to `Tools -> Options -> WindowsPerf -> WindowsPerf Path`. This step is crucial for utilizing the GUI, and the extension will not work if you don't do it.
94
+
To get started, you must link the GUI with the executable file `wperf.exe` by navigating to **Tools > Options > WindowsPerf > WindowsPerf Path**. This step is crucial for utilizing the GUI, and the extension will not work if you don't do it.
101
95
102
96
## Uninstall the WindowsPerfGUI extension
103
97
104
-
In Visual Studio go to `Extensions` -> `Manage Extensions` -> `Installed` -> `All` -> `WindowsPerfGUI` and select "Uninstall".
98
+
In Visual Studio go to **Extensions > Manage Extensions > Installed > All > WindowsPerfGUI** and select **Uninstall**.
105
99
106
-
Please note that this will be scheduled by Visual Studio. You may need to close VS instance and follow uninstall wizard to remove the extension.
100
+
As this will be scheduled by Visual Studio, you might need to close the VS instance and follow the uninstall wizard to remove the extension.
### Optional additional search terms (one per line) to assist in finding the article
14
+
additional_search_terms:
15
+
- perf
16
+
- profiling
17
+
- profiler
18
+
- windows
19
+
- woa
20
+
- windows on arm
21
+
- windows performance analyzer
22
+
- wpa
23
+
24
+
### FIXED, DO NOT MODIFY
25
+
weight: 1# Defines page ordering. Must be 1 for first (or only) page.
26
+
tool_install: true # Set to true to be listed in main selection page, else false
27
+
multi_install: FALSE # Set to true if first page of multi-page article, else false
28
+
multitool_install_part: false # Set to true if a sub-page of a multi-page article, else false
29
+
layout: installtoolsall # DO NOT MODIFY. Always true for tool install articles
30
+
---
31
+
32
+
## What is the Windows Performance Analyzer plugin?
33
+
34
+
The Windows Performance Analyzer plugin connects Windows Perf to the Windows Performance Analyzer (WPA).
35
+
36
+
[WindowsPerf](https://github.com/arm-developer-tools/windowsperf) is a lightweight performance profiling tool inspired by Linux Perf and designed for Windows on Arm.
37
+
38
+
Windows Performance Analyzer (WPA) is a tool that creates graphs and data tables of Event Tracing for Windows (ETW) events that are recorded by Windows Performance Recorder (WPR), Xperf, or an assessment that is run in the Assessment Platform. WPA opens event trace log (ETL) files for analysis.
39
+
40
+
The WPA plugin is built using the [Microsoft Performance Toolkit SDK](https://github.com/microsoft/microsoft-performance-toolkit-sdk), a collection of tools to create and extend performance analysis applications. The plugin parses json output from WidowsPerf so that it can be visualized in WPA.
41
+
42
+
## What are some of the features of the WPA plugin?
43
+
44
+
The WindowsPerf GUI extension is composed of several key features, each designed to streamline the user experience:
45
+
46
+
### What is the timeline view?
47
+
48
+
The timeline view visualizes the `wperf stat` timeline data plotted by event group.
49
+
50
+

51
+
52
+
### What is the telemetry view?
53
+
54
+
The telemetry view displays telemetry events grouped by unit.
Before using the WPA plugin, make sure you have installed WPA.
61
+
62
+
### Windows Performance Analyzer
63
+
64
+
WPA is included in the Windows Assessment and Deployment Kit (Windows ADK) that can be downloaded from [Microsoft](https://go.microsoft.com/fwlink/?linkid=2243390).
65
+
66
+
{{% notice Note %}}
67
+
The WPA plugin requires WPA version `11.0.7.2` or higher.
68
+
{{% /notice %}}
69
+
70
+
Run the downloaded `adksetup.exe` program.
71
+
72
+
Specify the default installation location and accept the license agreement.
73
+
74
+
Make sure that "Windows Performance Toolkit" is checked under "Select the features you want to install".
Copy file name to clipboardExpand all lines: content/learning-paths/cross-platform/gitlab/1-gitlab-runner.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,7 @@ A GitLab Runner works with GitLab CI/CD to run jobs in a pipeline. It acts as an
16
16
3. Multi-architecture support: GitLab runners support multiple architectures including - `x86/amd64` and `arm64`
17
17
18
18
## What is Google Axion?
19
-
Axion is Google’s first Arm-based server processor, built using the Armv9 Neoverse V2 CPU. The VM instances are part of the `C4A` family of compute instances. To learn more about Google Axion refer to this [blog](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu).
20
-
21
-
Note: These `C4A` VM instances are in public preview and needs a signup to be enabled in your Google Cloud account/project.
19
+
Axion is Google’s first Arm-based server processor, built using the Armv9 Neoverse V2 CPU. The VM instances are part of the `C4A` family of compute instances. To learn more about Google Axion refer to this [page](cloud.google.com/products/axion).
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/csp/google.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ layout: "learningpathall"
11
11
12
12
As with most cloud service providers, Google Cloud offers a pay-as-you-use [pricing policy](https://cloud.google.com/pricing), including a number of [free](https://cloud.google.com/free/docs/free-cloud-features) services.
13
13
14
-
This section is to help you get started with [Google Cloud Compute Engine](https://cloud.google.com/compute) compute services, using Arm-based [Tau T2A](https://cloud.google.com/tau-vm) Virtual Machines. This is a general-purpose compute platform, essentially your own personal computer in the cloud.
14
+
This section is to help you get started with [Google Cloud Compute Engine](https://cloud.google.com/compute) compute services, using Arm-based Virtual Machines. Google Cloud offers two generations of Arm-based VMs, `C4A` is the latest generation based on [Google Axion](cloud.google.com/products/axion), Google’s first Arm-based server processor, built using the Armv9 Neoverse V2 CPU. The previous generation VMs are based on Ampere Altra processor and part of [Tau T2A](https://cloud.google.com/tau-vm) family of Virtual Machines.
15
15
16
16
Detailed instructions are available in the Google Cloud [documentation](https://cloud.google.com/compute/docs/instances).
17
17
@@ -23,7 +23,7 @@ If using an organization's account, you will likely need to consult with your in
23
23
24
24
## Browse for an appropriate instance
25
25
26
-
Google Cloud offers a wide range of instance types, covering all performance (and pricing) points. For an overview of the Tau T2A instance types, see the [General-purpose machine family](https://cloud.google.com/compute/docs/general-purpose-machines#t2a_machines) overview.
26
+
Google Cloud offers a wide range of instance types, covering all performance (and pricing) points. For an overview of the `C4A` instance types, see this [page](cloud.google.com/products/axion). Similarly, to know more about the `T2A` instance types, see the [General-purpose machine family](https://cloud.google.com/compute/docs/general-purpose-machines#t2a_machines) overview.
27
27
28
28
Also note which [regions](https://cloud.google.com/compute/docs/regions-zones#available) these servers are available in.
29
29
@@ -49,15 +49,15 @@ Select an appropriate `region` and `zone` that support Arm-based servers.
49
49
50
50

51
51
52
-
To view the latest information on which available regions and zones support Arm-based servers, see the [Compute Engine documentation](https://cloud.google.com/compute/docs/regions-zones#available). To filter for Arm-based machines, click on `Select a machine type`, then select `T2A` from the pull-down menu.
52
+
To view the latest information on which available regions and zones support Arm-based servers, see the [Compute Engine documentation](https://cloud.google.com/compute/docs/regions-zones#available). To filter for Arm-based machines, click on `Select a machine type`, then select `T2A`or `C4A`from the pull-down menu.
53
53
54
54

55
55
56
56
### Machine configuration
57
57
58
-
Select `T2A` from the `Series` pull-down menu. Then select an appropriate `Machine type` configuration for your needs.
58
+
Select `C4A` from the `Series` pull-down menu. Then select an appropriate `Machine type` configuration for your needs.
59
59
60
-

60
+

0 commit comments