Deploy SqueezeNet 1.0 INT8 model with ONNX Runtime on Azure Cobalt 100

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

@@ -0,0 +1,59 @@
+---
+title: Deploy SqueezeNet 1.0 INT8 model with ONNX Runtime on Azure Cobalt 100
+
+minutes_to_complete: 60   
+
+who_is_this_for: This Learning Path introduces ONNX deployment on Microsoft Azure Cobalt 100 (Arm-based) virtual machines. It is designed for developers migrating ONNX-based applications from x86_64 to Arm with minimal or no changes.
+
+learning_objectives:
+    - Provision an Azure Arm64 virtual machine using Azure console, with Ubuntu Pro 24.04 LTS as the base image.
+    - Deploy ONNX on the Ubuntu Pro virtual machine.
+    - Perform ONNX baseline testing and benchmarking on both x86_64 and Arm64 virtual machines.
+
+prerequisites:
+    - A [Microsoft Azure](https://azure.microsoft.com/) account with access to Cobalt 100 based instances (Dpsv6).
+    - Basic understanding of Python and machine learning concepts.
+    - Familiarity with [ONNX Runtime](https://onnxruntime.ai/docs/) and Azure cloud services.
+
+author: Jason Andrews
+
+### Tags
+skilllevels: Advanced
+subjects: ML
+cloud_service_providers: Microsoft Azure
+
+armips:
+    - Neoverse
+
+tools_software_languages:
+    - Python
+    - ONNX Runtime
+
+operatingsystems:
+    - Linux
+
+further_reading:
+  - resource:
+      title: Azure Virtual Machines documentation
+      link: https://learn.microsoft.com/en-us/azure/virtual-machines/
+      type: documentation
+  - resource:
+        title: ONNX Runtime Docs
+        link: https://onnxruntime.ai/docs/
+        type: documentation
+  - resource:
+        title: ONNX (Open Neural Network Exchange) documentation
+        link: https://onnx.ai/
+        type: documentation
+  - resource:
+        title: onnxruntime_perf_test tool - ONNX Runtime performance benchmarking
+        link: https://onnxruntime.ai/docs/performance/tune-performance/profiling-tools.html#in-code-performance-profiling
+        type: documentation
+
+
+### FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 1                       # _index.md always has weight of 1 to order correctly
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+learning_path_main_page: "yes"  # This should be surfaced when looking for related content. Only set for _index.md of learning path content.
+---

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

@@ -0,0 +1,8 @@
+---
+# ================================================================================
+#       FIXED, DO NOT MODIFY THIS FILE
+# ================================================================================
+weight: 21                  # Set to always be larger than the content in this path to be at the end of the navigation.
+title: "Next Steps"         # Always the same, html page title.
+layout: "learningpathall"   # All files under learning paths have this same wrapper for Hugo processing.
+---

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

@@ -0,0 +1,21 @@
+---
+title: "Overview"
+
+weight: 2
+
+layout: "learningpathall"
+---
+
+## Cobalt 100 Arm-based processor
+
+Azure’s Cobalt 100 is built on Microsoft's first-generation, in-house Arm-based processor: the Cobalt 100. Designed entirely by Microsoft and based on Arm’s Neoverse N2 architecture, this 64-bit CPU delivers improved performance and energy efficiency across a broad spectrum of cloud-native, scale-out Linux workloads. These include web and application servers, data analytics, open-source databases, caching systems, and more. Running at 3.4 GHz, the Cobalt 100 processor allocates a dedicated physical core for each vCPU, ensuring consistent and predictable performance. 
+
+To learn more about Cobalt 100, refer to the blog [Announcing the preview of new Azure virtual machine based on the Azure Cobalt 100 processor](https://techcommunity.microsoft.com/blog/azurecompute/announcing-the-preview-of-new-azure-vms-based-on-the-azure-cobalt-100-processor/4146353).
+
+## ONNX  
+ONNX (Open Neural Network Exchange) is an open-source format designed for representing machine learning models.  
+It provides interoperability between different deep learning frameworks, enabling models trained in one framework (such as PyTorch or TensorFlow) to be deployed and run in another.  
+
+ONNX models are serialized into a standardized format that can be executed by the **ONNX Runtime**, a high-performance inference engine optimized for CPU, GPU, and specialized hardware accelerators. This separation of model training and inference allows developers to build flexible, portable, and production-ready AI workflows.  
+
+ONNX is widely used in cloud, edge, and mobile environments to deliver efficient and scalable inference for deep learning models. Learn more from the [ONNX official website](https://onnx.ai/) and the [ONNX Runtime documentation](https://onnxruntime.ai/docs/).    

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

@@ -0,0 +1,52 @@
+---
+title: Baseline Testing
+weight: 5
+
+### FIXED, DO NOT MODIFY
+layout: learningpathall
+---
+
+
+## Baseline testing using ONNX Runtime: 
+
+This test measures the inference latency of the ONNX Runtime by timing how long it takes to process a single input using the `squeezenet-int8.onnx model`. It helps evaluate how efficiently the model runs on the target hardware.
+
+Create a **baseline.py** file with the below code for baseline test of ONNX:
+
+```python
+import onnxruntime as ort
+import numpy as np
+import time
+
+session = ort.InferenceSession("squeezenet-int8.onnx")
+input_name = session.get_inputs()[0].name
+data = np.random.rand(1, 3, 224, 224).astype(np.float32)
+
+start = time.time()
+outputs = session.run(None, {input_name: data})
+end = time.time()
+
+print("Inference time:", end - start)
+```
+
+Run the baseline test:
+
+```console
+python3 baseline.py
+```
+You should see an output similar to:
+```output
+Inference time: 0.0026061534881591797
+```
+{{% notice Note %}}Inference time is the amount of time it takes for a trained machine learning model to make a prediction (i.e., produce output) after receiving input data. 
+input tensor of shape (1, 3, 224, 224): 
+- 1: batch size 
+- 3: color channels (RGB) 
+- 224 x 224: image resolution (common for models like SqueezeNet)
+{{% /notice %}}
+
+#### Output summary:
+
+- Single inference latency: ~2.60 milliseconds (0.00260 sec) 
+- This shows the initial (cold-start) inference performance of ONNX Runtime on CPU using an optimized int8 quantized model. 
+- This demonstrates that the setup is fully working, and ONNX Runtime efficiently executes quantized models on Arm64. 

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

@@ -0,0 +1,138 @@
+---
+title: Benchmarking via onnxruntime_perf_test
+weight: 6
+
+### FIXED, DO NOT MODIFY
+layout: learningpathall
+---
+
+Now that you’ve set up and run the ONNX model (e.g., SqueezeNet), you can use it to benchmark inference performance using Python-based timing or tools like **onnxruntime_perf_test**. This helps evaluate the ONNX Runtime efficiency on Azure Arm64-based Cobalt 100 instances.
+
+You can also compare the inference time between Cobalt 100 (Arm64) and similar D-series x86_64-based virtual machine on Azure.
+
+## Run the performance tests using onnxruntime_perf_test
+The **onnxruntime_perf_test** is a performance benchmarking tool included in the ONNX Runtime source code. It is used to measure the inference performance of ONNX models under various runtime conditions (like CPU, GPU, or other execution providers).
+
+### Install Required Build Tools
+
+```console
+sudo apt update
+sudo apt install -y build-essential cmake git unzip pkg-config
+sudo apt install -y protobuf-compiler libprotobuf-dev libprotoc-dev git
+```
+Then verify:
+```console
+protoc --version
+```
+You should see an output similar to:
+
+```output
+libprotoc 3.21.12
+```
+### Build ONNX Runtime from Source:
+
+The benchmarking tool, **onnxruntime_perf_test**, isn’t available as a pre-built binary artifact for any platform. So, you have to build it from the source, which is expected to take around 40-50 minutes. 
+
+Clone onnxruntime:
+```console
+git clone --recursive https://github.com/microsoft/onnxruntime 
+cd onnxruntime
+```
+Now, build the benchmark as below:
+
+```console
+./build.sh --config Release --build_dir build/Linux --build_shared_lib --parallel --build --update --skip_tests 
+```
+This will build the benchmark tool inside ./build/Linux/Release/onnxruntime_perf_test. 
+
+### Run the benchmark
+Now that the benchmarking tool has been built, you can benchmark the **squeezenet-int8.onnx** model, as below:
+
+```console
+./build/Linux/Release/onnxruntime_perf_test -e cpu -r 100 -m times -s -Z -I <path-to-squeezenet-int8.onnx>
+```
+- **e cpu**: Use the CPU execution provider (not GPU or any other backend). 
+- **r 100**: Run 100 inferences. 
+- **m times**: Use "repeat N times" mode. 
+- **s**: Show detailed statistics. 
+- **Z**: Disable intra-op thread spinning (reduces CPU usage when idle between runs). 
+- **I**: Input the ONNX model path without using input/output test data.
+
+You should see an output similar to:
+
+```output
+Disabling intra-op thread spinning between runs
+Session creation time cost: 0.0102016 s
+First inference time cost: 2 ms
+Total inference time cost: 0.185739 s
+Total inference requests: 100
+Average inference time cost: 1.85739 ms
+Total inference run time: 0.18581 s
+Number of inferences per second: 538.184
+Avg CPU usage: 96 %
+Peak working set size: 36696064 bytes
+Avg CPU usage:96
+Peak working set size:36696064
+Runs:100
+Min Latency: 0.00183404 s
+Max Latency: 0.00190312 s
+P50 Latency: 0.00185674 s
+P90 Latency: 0.00187215 s
+P95 Latency: 0.00187393 s
+P99 Latency: 0.00190312 s
+P999 Latency: 0.00190312 s
+```
+### Benchmark Metrics Explained  
+
+- **Average Inference Time**: The mean time taken to process a single inference request across all runs. Lower values indicate faster model execution.  
+- **Throughput**: The number of inference requests processed per second. Higher throughput reflects the model’s ability to handle larger workloads efficiently.  
+- **CPU Utilization**: The percentage of CPU resources used during inference. A value close to 100% indicates full CPU usage, which is expected during performance benchmarking.  
+- **Peak Memory Usage**: The maximum amount of system memory (RAM) consumed during inference. Lower memory usage is beneficial for resource-constrained environments. 
+- **P50 Latency (Median Latency)**: The time below which 50% of inference requests complete. Represents typical latency under normal load.   
+- **Latency Consistency**: Describes the stability of latency values across all runs. "Consistent" indicates predictable inference performance with minimal jitter.  
+
+### Benchmark summary on Arm64:
+Here is a summary of benchmark results collected on an Arm64 **D4ps_v6 Ubuntu Pro 24.04 LTS virtual machine**.
+
+| **Metric**                | **Value** |
+|----------------------------|-------------------------------|
+| **Average Inference Time** | 1.857 ms                     |
+| **Throughput**             | 538.18 inferences/sec        |
+| **CPU Utilization**        | 96%                          |
+| **Peak Memory Usage**      | 36.70 MB                     |
+| **P50 Latency**            | 1.857 ms                     |
+| **P90 Latency**            | 1.872 ms                     |
+| **P95 Latency**            | 1.874 ms                     |
+| **P99 Latency**            | 1.903 ms                     |
+| **P999 Latency**           | 1.903 ms                     |
+| **Max Latency**            | 1.903 ms                     |
+| **Latency Consistency**    | Consistent                   |
+
+
+### Benchmark summary on x86
+Here is a summary of benchmark results collected on x86 **D4s_v6 Ubuntu Pro 24.04 LTS virtual machine**.
+
+| **Metric**                | **Value on Virtual Machine** |
+|----------------------------|-------------------------------|
+| **Average Inference Time** | 1.413 ms                     |
+| **Throughput**             | 707.48 inferences/sec        |
+| **CPU Utilization**        | 100%                         |
+| **Peak Memory Usage**      | 38.80 MB                     |
+| **P50 Latency**            | 1.396 ms                     |
+| **P90 Latency**            | 1.501 ms                     |
+| **P95 Latency**            | 1.520 ms                     |
+| **P99 Latency**            | 1.794 ms                     |
+| **P999 Latency**           | 1.794 ms                     |
+| **Max Latency**            | 1.794 ms                     |
+| **Latency Consistency**    | Consistent                   |
+
+
+### Highlights from Ubuntu Pro 24.04 Arm64 Benchmarking
+
+When comparing the results on Arm64 vs x86_64 virtual machines:
+- **Low-Latency Inference:** Achieved consistent average inference times of ~1.86 ms on Arm64.  
+- **Strong and Stable Throughput:** Sustained throughput of over 538 inferences/sec using the `squeezenet-int8.onnx` model on D4ps_v6 instances.  
+- **Lightweight Resource Footprint:** Peak memory usage stayed below 37 MB, with CPU utilization around 96%, ideal for efficient edge or cloud inference.  
+- **Consistent Performance:** P50, P95, and Max latency remained tightly bound, showcasing reliable performance on Azure Cobalt 100 Arm-based infrastructure.
+
+You have now benchmarked ONNX on an Azure Cobalt 100 Arm64 virtual machine and compared results with x86_64.

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

@@ -0,0 +1,50 @@
+---
+title: Create an Arm based cloud virtual machine using Microsoft Cobalt 100 CPU 
+weight: 3
+
+### FIXED, DO NOT MODIFY
+layout: learningpathall
+---
+
+## Introduction
+
+There are several ways to create an Arm-based Cobalt 100 virtual machine : the Microsoft Azure console, the Azure CLI tool, or using your choice of IaC (Infrastructure as Code). This guide will use the Azure console to create a virtual machine with Arm-based Cobalt 100 Processor. 
+
+This learning path focuses on the general-purpose virtual machine of the D series. Please read the guide on [Dpsv6 size series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dpsv6-series) offered by Microsoft Azure.  
+
+If you have never used the Microsoft Cloud Platform before, please review the microsoft [guide to Create a Linux virtual machine in the Azure portal](https://learn.microsoft.com/en-us/azure/virtual-machines/linux/quick-create-portal?tabs=ubuntu). 
+
+#### Create an Arm-based Azure Virtual Machine 
+
+Creating a virtual machine based on Azure Cobalt 100 is no different from creating any other virtual machine in Azure. To create an Azure virtual machine, launch the Azure portal and navigate to "Virtual Machines".
+1. Select "Create", and click on "Virtual Machine" from the drop-down list.
+2. Inside the "Basic" tab, fill in the Instance details such as "Virtual machine name" and "Region".
+3. Choose the image for your virtual machine (for example, Ubuntu Pro 24.04 LTS) and select “Arm64” as the VM architecture.
+4. In the “Size” field, click on “See all sizes” and select the D-Series v6 family of virtual machines. Select “D4ps_v6” from the list.
+
+![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance.png "Figure 1: Select the D-Series v6 family of virtual machines")
+
+5. Select "SSH public key" as an Authentication type. Azure will automatically generate an SSH key pair for you and allow you to store it for future use. It is a fast, simple, and secure way to connect to your virtual machine.
+6. Fill in the Administrator username for your VM.
+7. Select "Generate new key pair", and select "RSA SSH Format" as the SSH Key Type. RSA could offer better security with keys longer than 3072 bits. Give a Key pair name to your SSH key.
+8. In the "Inbound port rules", select HTTP (80) and SSH (22) as the inbound ports.
+
+![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance1.png "Figure 2: Allow inbound port rules")
+
+9. Click on the "Review + Create" tab and review the configuration for your virtual machine. It should look like the following:
+
+![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/ubuntu-pro.png "Figure 3: Review and Create an Azure Cobalt 100 Arm64 VM")
+
+10. Finally, when you are confident about your selection, click on the "Create" button, and click on the "Download Private key and Create Resources" button.
+
+![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance4.png "Figure 4: Download Private key and Create Resources")
+
+11. Your virtual machine should be ready and running within no time. You can SSH into the virtual machine using the private key, along with the Public IP details.
+
+![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/final-vm.png "Figure 5: VM deployment confirmation in Azure portal")
+
+{{% notice Note %}}
+
+To learn more about Arm-based virtual machine in Azure, refer to “Getting Started with Microsoft Azure” in [Get started with Arm-based cloud instances](/learning-paths/servers-and-cloud-computing/csp/azure).
+
+{{% /notice %}}