Skip to content

Commit e6b5596

Browse files
Improve clarity and consistency in documentation for ONNX Runtime testing and Azure VM creation.
1 parent 34ac528 commit e6b5596

File tree

3 files changed

+16
-17
lines changed

3 files changed

+16
-17
lines changed

content/learning-paths/servers-and-cloud-computing/onnx-on-azure/baseline.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,14 +36,13 @@ python3 baseline.py
3636
You should see output similar to:
3737
```output
3838
Inference time: 0.0026061534881591797
39-
```
4039
{{% notice Note %}}
41-
Inference time is the amount of time it takes for a trained machine learning model to make a prediction (produce output) after receiving input data.
40+
Inference time is how long it takes for a trained machine learning model to make a prediction after it receives input data.
4241
43-
The input tensor has the shape `(1, 3, 224, 224)`, which means:
44-
- 1: batch size (number of images processed at once)
45-
- 3: color channels (RGB)
46-
- 224 x 224: image resolution (common for models like SqueezeNet)
42+
The input tensor shape `(1, 3, 224, 224)` means:
43+
- `1`: One image is processed at a time (batch size)
44+
- `3`: Three color channels (red, green, blue)
45+
- `224 x 224`: Each image is 224 pixels wide and 224 pixels tall (standard for SqueezeNet)
4746
{{% /notice %}}
4847
4948
This indicates the model successfully executed a single forward pass through the SqueezeNet INT8 ONNX model and returned results.

content/learning-paths/servers-and-cloud-computing/onnx-on-azure/benchmarking.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Now that you have validated ONNX Runtime with Python-based timing (for example,
1111

1212
This approach helps you evaluate ONNX Runtime efficiency on Azure Arm64-based Cobalt 100 instances and compare results with other architectures if needed.
1313

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.
1515

1616

1717
## Run the performance tests using onnxruntime_perf_test
@@ -35,7 +35,7 @@ You should see output similar to:
3535
```output
3636
libprotoc 3.21.12
3737
```
38-
### Build ONNX Runtime from source
38+
## Build ONNX Runtime from source
3939

4040
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.
4141

@@ -65,12 +65,12 @@ Now that you have built the benchmarking tool, you can run inference benchmarks
6565

6666
Breakdown of the flags:
6767

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.
7474

7575
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.
7676

content/learning-paths/servers-and-cloud-computing/onnx-on-azure/create-instance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,15 +39,15 @@ Creating a virtual machine based on Azure Cobalt 100 is no different from creati
3939

4040
![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance1.png "Allow inbound port rules")
4141

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:
4343

4444
![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/ubuntu-pro.png "Review and Create an Azure Cobalt 100 Arm64 VM")
4545

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.
4747

4848
![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance4.png "Download Private key and Create Resources")
4949

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.
5151

5252
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.
5353

0 commit comments

Comments
 (0)