[doc] Refresh the documentation for DeepSeek-V3.2

[Nagisa125]

What this PR does / why we need it?

Updated the DSV32 document.

1. Changed the PD separation boot mode to layerwise.
2. Changed max-num-batched-tokens to a multiple of the TP to avoid triggering a verification error.
3. Added a link to help users adjust the configuration.

Does this PR introduce any user-facing change?

How was this patch tested?

• vLLM version: v0.17.0
• vLLM main: vllm-project/vllm@4497431

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refreshes the documentation for DeepSeek-V3.2, focusing on refining the configuration and deployment instructions for distributed environments. The changes ensure that the provided examples and parameters are up-to-date with the latest system requirements and connector implementations, enhancing the accuracy and utility of the tutorial for users.

Highlights

• Configuration Updates: The --max-num-batched-tokens parameter was updated from 32550 to 32560 in several server startup commands.
• KV Connector Renaming: The kv_connector type was changed from MooncakeConnectorV1 to MooncakeLayerwiseConnector across various kv-transfer-config settings.
• Environment Variable Removal: The PYTORCH_NPU_ALLOC_CONF=expandable_segments:True environment variable setting was removed from the documentation.
• Documentation Reference: A new reference link to the 'Distributed DP Server With Large-Scale Expert Parallelism' guide was added for detailed boot methods.
• Proxy Script Changes: The example proxy script name was updated from load_balance_proxy_server_example.py to load_balance_proxy_layerwise_server_example.py, and its default --host IP was changed from 0.0.0.0 to 141.61.39.105.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

[github-actions]

👋 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.

[MengqingCao]

LGTM, @rjg-lyh PTAL