triton-inference-server / triton-inference-server/server
support decoupled mode in perf_analyzer
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11k
- Forks
- 1.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 28
Description
when using perf_analyzer to analyze a python decoupled model like triton-decoupled using command below
perf_analyzer -i grpc --streaming -m repeat --concurrency-range 1:2 -vv --input-data repeat_data.json
repeat_data.json
{
"data" :
[
{
"IN" : [5]
}
]
}
which 5 means how many response will server (decouple mode) will send to client
the results will show error
No valid requests recorded within time interval. Please use a larger time window.
it seems like perf_analyzer will send a request when it get a response, but in decouple mode, perf_analyzer should not send request again until it get final response from decouple mode
Contributor guide
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 the perf_analyzer CLI command and repeat_data.json shown in the issue, reproducing it against the linked triton-decoupled Python model. Trace how streaming responses are handled, then verify that five decoupled responses complete as one request and that the reported time-window error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100