Repository navigation
docs(site): explain CPU transcription memory, timing and workload limits - #3933
Merged
Merged
Conversation
Rewrite the bilingual CPU guide around model/runtime boundaries, memory, RTF, request latency and workload evaluation. Preserve URLs and publication dates; label invented arithmetic and remove unbounded benchmark claims. No new model inference or downloads. Signed-off-by: LauraGPT <zhifu.gzf@alibaba-inc.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Substantially revise the existing bilingual CPU article,
lightweight-speech-recognition-cpu, for beginners and application agents. Explain how to evaluate a recording-to-final-text workload using quality, memory, timing and concurrency instead of unqualified benchmark promises.Validation
Scope
This is a conceptual guide, not a new installation tutorial or performance report. Official source/documents at
581150d8e1de2bc055cc390b6f2efc9ea78b48b7support the boundaries. No new model inference, weights, API purchases or production model-service changes. No accuracy, speed, adoption or growth claim. Nano remains deferred.Only five website content/metadata/test paths change. Static deployment is a separate authorized operation after normal merge; this PR alone does not prove the page is live.