Skip to content

Conversation

Potabk
Copy link
Collaborator

@Potabk Potabk commented Sep 28, 2025

What this PR does / why we need it?

  1. Add deepseek-v3.1-bf16 multi-node mp backend tutorial
  2. Add deepseek-v3.1-w8a8 tp16 single node on a3 turorial

Does this PR introduce any user-facing change?

How was this patch tested?

Copy link

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

  • A PR should do only one thing, smaller PRs enable faster reviews.
  • Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
  • Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Sep 28, 2025
@Potabk Potabk marked this pull request as draft September 28, 2025 03:16
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds documentation for multi-node deployment of DeepSeek models. The new documentation file multi_node_deepseek.md contains several critical and high-severity issues that would prevent users from successfully following the tutorials. My review includes corrections for:

  • Incorrect device mappings in the docker run command for the specified hardware.
  • Inconsistent and incorrect model configurations in the multi-node BF16 tutorial, including model name, batch token limits, and environment variables.
  • A misleading comment in the BF16 tutorial.
  • A confusing documentation structure where a single-node tutorial is placed within a multi-node guide.
    Applying these suggestions will significantly improve the correctness and clarity of the documentation.

Signed-off-by: wangli <[email protected]>
@Potabk Potabk requested review from Yikun and wangxiyuan September 29, 2025 11:02
@Yikun Yikun mentioned this pull request Sep 29, 2025
wangxiyuan added a commit that referenced this pull request Sep 29, 2025
### What this PR does / why we need it?

This PR added the initial DeepSeek V3.2 support with [vLLM
v0.11.0](https://github.com/vllm-project/vllm/tree/releases/v0.11.0)
(not released yet). We will complete vLLM adaptation as soon as
possible. This feature will be ready in recent 1-2 days.

Related doc: #3223 .

### Does this PR introduce _any_ user-facing change?
Yes!

### How was this patch tested?
CI passed and Run deepseek doc soon.


- vLLM version: v0.11.0rc3
- vLLM main:
vllm-project/vllm@releases/v0.11.0

---------

Signed-off-by: wangxiyuan <[email protected]>
Signed-off-by: zzzzwwjj <[email protected]>
Signed-off-by: linfeng-yuan <[email protected]>
Signed-off-by: wxsIcey <[email protected]>
Signed-off-by: MengqingCao <[email protected]>
Co-authored-by: zzzzwwjj <[email protected]>
Co-authored-by: linfeng-yuan <[email protected]>
Co-authored-by: wxsIcey <[email protected]>
Co-authored-by: MengqingCao <[email protected]>
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation merge-conflicts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants