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/learning-paths/servers-and-cloud-computing/onnx-on-azure/benchmarking.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Now that you have validated ONNX Runtime with Python-based timing (for example,
11
11
12
12
This approach helps you evaluate ONNX Runtime efficiency on Azure Arm64-based Cobalt 100 instances and compare results with other architectures if needed.
13
13
14
-
You are ready to run benchmarks — a key skill for optimizing real-world deployments.
14
+
You are ready to run benchmarks, which is a key skill for optimizing real-world deployments.
15
15
16
16
17
17
## Run the performance tests using onnxruntime_perf_test
@@ -35,7 +35,7 @@ You should see output similar to:
35
35
```output
36
36
libprotoc 3.21.12
37
37
```
38
-
###Build ONNX Runtime from source
38
+
## Build ONNX Runtime from source
39
39
40
40
The benchmarking tool `onnxruntime_perf_test` isn’t available as a pre-built binary for any platform, so you will need to build it from source. This process can take up to 40 minutes.
41
41
@@ -65,12 +65,12 @@ Now that you have built the benchmarking tool, you can run inference benchmarks
65
65
66
66
Breakdown of the flags:
67
67
68
-
-`-e cpu`: Use the CPU execution provider.
69
-
-`-r 100`: Run 100 inference passes for statistical reliability.
70
-
-`-m times`: Run in “repeat N times” mode for latency-focused measurement.
71
-
-`-s`: Print summary statistics after the run.
72
-
-`-Z`: Disable memory arena for more consistent timing.
73
-
-`-I ../squeezenet-int8.onnx`: Path to your ONNX model file.
68
+
-`-e cpu`: use the CPU execution provider.
69
+
-`-r 100`: run 100 inference passes for statistical reliability.
70
+
-`-m times`: run in “repeat N times” mode for latency-focused measurement.
71
+
-`-s`: print summary statistics after the run.
72
+
-`-Z`: disable memory arena for more consistent timing.
73
+
-`-I ../squeezenet-int8.onnx`: path to your ONNX model file.
74
74
75
75
You should see output with latency and throughput statistics. If you encounter build errors, check that you have enough memory (at least 8 GB recommended) and all dependencies are installed. For missing dependencies, review the installation steps above.
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/onnx-on-azure/create-instance.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,15 +39,15 @@ Creating a virtual machine based on Azure Cobalt 100 is no different from creati
39
39
40
40

41
41
42
-
-Click on the **Review + Create** tab and review the configuration for your virtual machine. It should look like the following:
42
+
Click on the **Review + Create** tab and review the configuration for your virtual machine. It should look like the following:
43
43
44
44

45
45
46
-
-When you are confident about your selection, click on the **Create** button, and click on the **Download Private key and Create Resources** button.
46
+
When you are confident about your selection, click on the **Create** button, and click on the **Download Private key and Create Resources** button.
47
47
48
48

49
49
50
-
-Your virtual machine should be ready and running within a few minutes. You can SSH into the virtual machine using the private key, along with the Public IP details.
50
+
Your virtual machine should be ready and running within a few minutes. You can SSH into the virtual machine using the private key, along with the Public IP details.
51
51
52
52
You should see your VM listed as **Running** in the Azure portal. If you have trouble connecting, double-check your SSH key and ensure the correct ports are open. If the VM creation fails, check your Azure quota, region availability, or try a different VM size.
0 commit comments