Benchmarks
Echophrase is built on Tauri + Rust instead of Electron, and we measured exactly what that buys you. These are first-party numbers, but they’re honest ones: where a figure is an estimate or a comparison is indirect, we say so.TL;DR
Measured 2026-07-06 with NVIDIA Parakeet-TDT 0.6B v3 (the default model) loaded:
A single transcription is a marginal blip - a fraction of a watt-second and a
few megabytes - then everything settles back to the ready state.
Install size
The extracted Windows app is 34.2 MB. For context: any Electron-based app carries a ~200 MB runtime (bundled Chromium + Node + V8) before a single line of app code is added - Echophrase’s entire install is roughly 6x smaller than that empty floor. Real Electron apps commonly land at 300-500 MB installed. Sources for the Electron runtime figures (independent 2026 framework comparisons, not our own measurements): Tech Insider, Hopp, codenote.net.Memory behavior: not a leak
RAM and VRAM rise after the first couple of transcriptions (226.6 → 390.7 MB RAM), which can look leak-like. We stress-tested it: after ~5 more back-to-back utterances with no restart, RAM moved from 385.31 MB to just 385.48 MB and VRAM held flat.
The initial rise is a one-time warm-up buffer/cache that plateaus and
stays flat regardless of how many phrases follow - a sustainable, always-ready
footprint rather than one that degrades over a session.
Methodology
Hardware: NVIDIA GeForce RTX 5080. Model: NVIDIA Parakeet-TDT 0.6B v3.
GPU power/VRAM/utilization sampled via one long-lived
nvidia-smi --query-gpu ... -lms process; RAM/CPU via PowerShell
Get-Process, with %CPU computed Task-Manager-style (delta CPU-seconds ÷
delta wall-seconds ÷ logical cores). Sampler overhead is small but not zero -
treat these as close estimates, not lab-isolated numbers. The GPU idle floor
also drifts between sessions with unrelated system activity, so each run
captures a fresh baseline.