Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] What is the difference between gptManagerBenchmark and gptSessionBenchmark in cpp benchmarks? #2092

Closed
hcnhcn012 opened this issue Aug 6, 2024 · 2 comments
Assignees
Labels
question Further information is requested triaged Issue has been triaged by maintainers

Comments

@hcnhcn012
Copy link

version of TensorRT-LLM: v0.11.0

What is the difference between gptManagerBenchmark and gptSessionBenchmark in cpp benchmarks, please give me some example scenarios of using each benchmark script, thans a lot :)

@yuhengxnv
Copy link

gptSessionBenchmark seems to be simpler to use, but it's recommended to use gptManagerBenchmark.

@lfr-0531 lfr-0531 added the question Further information is requested label Sep 2, 2024
@lfr-0531
Copy link
Collaborator

lfr-0531 commented Sep 2, 2024

The gptSessionBenchmark is used to benchmark the running with GptSession runtime, which can only support the static batching and is deprecated now. The gptManagerBenchmark is used to benchmark the executor and gptManager runtime, and it can support both static batching and inflight batching. Since GptSession will be removed in a future release, we recommand using gptManagerBenchmark. For the benchmark script, plz refer to the cpp benchmark README: https://github.com/NVIDIA/TensorRT-LLM/tree/main/benchmarks/cpp#benchmark-c-runtime

@lfr-0531 lfr-0531 self-assigned this Sep 4, 2024
@lfr-0531 lfr-0531 added the triaged Issue has been triaged by maintainers label Sep 4, 2024
@lfr-0531 lfr-0531 closed this as completed Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested triaged Issue has been triaged by maintainers
Projects
None yet
Development

No branches or pull requests

3 participants