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

[ChatQnA] Switch to vLLM as default llm backend on Gaudi #1404

Merged
merged 14 commits into from
Jan 17, 2025

Conversation

wangkl2
Copy link
Collaborator

@wangkl2 wangkl2 commented Jan 16, 2025

Description

Switching from TGI to vLLM as the default LLM serving backend on Gaudi for the ChatQnA example to enhance the perf. Via benchmarking on Gaudi2 server with vLLM and TGI backend for LLM component for different ISL/OSL and various number of queries and concurrency, the geomean of measured LLMServe perf on a 7B model shows perf improvement of vLLM over TGI on several metrics including average total latency, average TPOT and throughput, while the geomean of average TTFT does not increase significantly. TGI is still offered as an option to deploy for LLM serving. Besides, vLLM LLM also replaces TGI LLM for other provided E2E ChatQnA pipelines including without-rerank pipeline and megaservice with guardrails. This PR also aligns the parameters of llm service in all chatqna test scripts with what in readme file.

Issues

#1213

Type of change

  • New feature (non-breaking change which adds new functionality)
  • Others (enhancement, documentation, validation, etc.)

Dependencies

n/a

Tests

TGI-Gaudi version: 2.0.6
vLLM-fork version: 0.6.3.dev910+g3c39626f

Benchmark and compare the LLMServe perf on Gaudi2 server with OOB-vLLM and Tuned-TGI backend via GenAIEval. Below table shows the referenced geomean perf ratio on 7B LLM with 4 sets of ISL/OSL, measured on different num_queries and concurrency, including 32/8, 128/32. Leveraging vLLM as LLM backend shows 1.14X-6.39X perf speedup on 3 metrics but not significant perf drop on avg TTFT.

ISL/OSL, LLM Backend Geomean of Normalized Avg Total Latency Geomean of Normalized Avg TTFT Geomean of Normalized Avg TPOT Geomean of Normalized Output Tokens/s
128/128, TGI 1.00 1.00 1.00 1.00
128/128, vLLM 0.72 0.97 0.83 4.41
128/1024, TGI 1.00 1.00 1.00 1.00
128/1024, vLLM 0.97 0.94 0.97 5.10
1024/128, TGI 1.00 1.00 1.00 1.00
1024/128, vLLM 1.11 1.91 0.69 3.41
1024/1024, TGI 1.00 1.00 1.00 1.00
1024/1024, vLLM 0.77 1.01 0.87 21.76
Overall Geomean of Normalized Metric with vLLM 0.88 1.15 0.83 6.39
Overall Geomean Perf Speedup with vLLM over TGI 1/0.88=1.14X 1/1.15=0.87X 1/0.83=1.20X 6.39/1=6.39X

Switching from TGI to vLLM as the default LLM serving backend on Gaudi for the ChatQnA example to enhance the perf. Via benchmarking on Gaudi2 server with vLLM and TGI backend for LLM component for different ISL/OSL and various number of queries and concurrency, the geomean of measured LLMServe perf on a 7B model shows perf improvement of vLLM over TGI on several metrics including average total latency, average TPOT and throughput, while the geomean of average TTFT does not increase significantly. TGI is still offered as an option to deploy for LLM serving. Besides, vLLM LLM also replaces TGI LLM for other provided E2E ChatQnA pipelines including without-rerank pipeline and megaservice with guardrails.

Implement opea-project#1213

Signed-off-by: Wang, Kai Lawrence <[email protected]>
Signed-off-by: Wang, Kai Lawrence <[email protected]>
Signed-off-by: Wang, Kai Lawrence <[email protected]>
Signed-off-by: Wang, Kai Lawrence <[email protected]>
Signed-off-by: Wang, Kai Lawrence <[email protected]>
Signed-off-by: Wang, Kai Lawrence <[email protected]>
Signed-off-by: Wang, Kai Lawrence <[email protected]>
Copy link

github-actions bot commented Jan 16, 2025

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

@chensuyue chensuyue merged commit 00e9da9 into opea-project:main Jan 17, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants