PaddlePaddle / PaddlePaddle/FastDeploy
请求 fastdeploy_serving 服务器，不同的请求方式性能差距很大，这是什么原因导致的？
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 756
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 4
Description
复现文档：https://github.com/PaddlePaddle/FastDeploy/blob/develop/serving/docs/zh_CN/client.md
对比：1、使用tritonclient （grpc/http）客户端请求服务 ，耗时 0.4s
2、使用requests请求服务 ，耗时 4s
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with serving/docs/zh_CN/client.md and reproduce the TritonClient gRPC/HTTP and requests-based calls described there. Compare the request paths and timings, then document the confirmed cause of the difference and the guidance or change needed to make the behavior clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100