Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Nemotron 3.5 Streaming ASR Benchmarked on Pixel 11

AI summary

PyTorch profiled multilingual Nemotron 3.5 streaming ASR through ExecuTorch on a Google Pixel 11, testing chunk sizes, FP16 and QC8W precision, and Arm SME2 acceleration. With SME2 enabled, processing a 24.9-second recording fell from 9.79 to 4.61 seconds for FP16 and from 5.20 to 3.24 seconds for QC8W. The study also shows the accuracy-latency tradeoff: longer audio chunks improved word error rate but increased estimated time to first token.

In-depth insight

The case study gives edge-AI developers device-level measurements for jointly evaluating streaming-ASR accuracy, latency, quantization and Arm CPU acceleration, though the results come from one PyTorch-authored study on one smartphone.

When you’re speaking to a device, you expect text to appear as you talk. That makes streaming automatic speech recognition (ASR) a different challenge from batch transcription, where the model has the complete recording before it starts. Strong batch accuracy does not necessarily carry over into streaming. One cross-model ASR study illustrates this gap. Qwen3-ASR-1.7B achieved the best batch accuracy among the models tested, but its word error rate (WER) rose by 77% when evaluated with 2.4-second audio chunks.

In that study’s cross-model streaming comparison (Table 5), NVIDIA® Nemotron

™

Speech Streaming 0.6B had the lowest average streaming WER when operating over 560 ms audio chunks. The comparison makes a critical point: accuracy must be measured at the chunk cadence used in deployment.

This case study takes the newer, multilingual Nemotron 3.5 from PyTorch to ExecuTorch and profiles its on-device execution on a Google Pixel 11. We ask how precision and chunk size change streaming quality, how much processing time the audio requires with one inference thread, where the workload spends its time, and which native kernels run. The goal is a practical way to evaluate accuracy and latency together.

#Nemotron 3.5#PyTorch#ExecuTorch#Google Pixel 11#Arm SME2#XNNPACK#KleidiAI#NVIDIA Nemotron Speech Streaming 0.6B#Qwen3-ASR-1.7B

Original · 9 min readRead the original
Group chat

No comments yet. Start the conversation.