adityanandanx / adityanandanx/heimdall

Grilling: NPU as the default OCR engine?

未关闭
#68 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
wayfinder:grilling
主要语言
Python
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

描述

Part of #65

Blocked by: [Prototype: standalone NPU-vs-CPU OCR bench in the proto worktree](https://github.com/adityanandanx/heimdall/issues/67)

## Question

Given the prototype numbers: **does RapidOCR-on-NPU become heimdall's default OCR engine** (replacing the onnxruntime/CPU RapidOCR path in `src/heimdall/capture/ocr.py`)?

Weigh: per-frame latency vs CPU; cold-init cost (daemon start / engine warm-up); robustness over a session (watchdog/failure → auto-fallback to CPU?), recompile-on-shape-change behavior; and the CPU-usage win that motivated the question in the first place.

Resolution of this grilling = the **decision** that closes the map (Destination in #65): NPU-default, NPU-opt-in-behind-CPU, or stay CPU — stated with the tradeoffs and one-line recommendation for the follow-up implementation effort.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。