deployment-serving
Use PaddleSpeech server/client, HTTP and WebSocket APIs, offline and streaming configs, Paddle Inference, ONNX, C++ runtime, and deployment troubleshooting safely.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- deployment-serving
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Use PaddleSpeech server/client, HTTP and WebSocket APIs, offline and streaming configs, Paddle Inference, ONNX, C++ runtime, and deployment troubleshooting safely.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档references/api-contracts.md2.1 KB
- 参考文档references/runtime-deployment.md1.8 KB
- 参考文档references/server-and-streaming.md2.3 KB
- 参考文档references/troubleshooting.md1.4 KB
- 脚本scripts/inspect_server_config.py2.7 KB
03 SKILL.md 正文
Deployment and Serving
Use this sub-skill for paddlespeech_server, paddlespeech_client, PaddleSpeech Serving config YAML, HTTP REST APIs, WebSocket streaming ASR/TTS, online TTS, ACS, Paddle Inference/static models, ONNX streaming, C++ runtime, mobile/ARM deployment orientation, and service troubleshooting.
Safe Serving Workflow
-
Inspect the config before launch:
python scripts/inspect_server_config.py --config application.yaml -
Confirm side effects: server startup downloads/warmups models, opens ports, and runs until stopped.
-
Start only after approval:
paddlespeech_server start --config_file application.yaml -
Use the matching client:
paddlespeech_client asr --server_ip 127.0.0.1 --port 8090 --input input_16k.wav paddlespeech_client tts --server_ip 127.0.0.1 --port 8090 --input "您好" --output output.wav paddlespeech_client tts_online --server_ip 127.0.0.1 --port 8092 --protocol http --input "您好" --output output.wav
Route by Deployment Surface
- Offline HTTP ASR/TTS/CLS/TEXT/VECTOR/ACS: read
references/server-and-streaming.mdandreferences/api-contracts.md. - Streaming ASR: WebSocket-only ASR endpoint; use a WebSocket config and
paddlespeech_client asr_online. - Streaming TTS: HTTP or WebSocket depending on
protocol; online or online-ONNX engine types. - Paddle Inference/static: use static model configs and predictor sections; do not mix dynamic checkpoints.
- C++/mobile/Android/ARM/FastDeploy: read
references/runtime-deployment.md; treat builds as toolchain workflows requiring approval. - Audio search / ACS / Milvus apps: use this sub-skill for service boundaries and external service planning; route embedding details to
../audio-analysis/SKILL.md.
References and Helper
references/server-and-streaming.mdexplains config fields, engine lists, protocols, and client commands.references/api-contracts.mdsummarizes REST and WebSocket routes and payload expectations.references/runtime-deployment.mdcovers static/Paddle Inference, ONNX, C++ runtime, Android/ARM, Docker, and audio-search boundaries.references/troubleshooting.mdcovers ports, host binding, protocol mismatch, engine warmup, and service dependencies.scripts/inspect_server_config.pysafely validates YAML structure without starting a server.
Do Not Do by Default
- Do not start server processes, Docker Compose, Milvus/MySQL, C++ builds, Android/ARM builds, or streaming demos without approval.
- Do not claim server readiness from CLI help; warmup and model downloads are separate runtime checks.
- Do not use HTTP clients against WebSocket streaming ASR configs or offline configs against online engine types.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).