Skip to content

Conversation

wangln19
Copy link
Contributor

Signed-off-by: wangln19 [email protected]

Signed-off-by: wangln19 <[email protected]>
Copy link
Contributor

Summary of Changes

Hello @wangln19, I'm Gemini Code Assist1! 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 enhances the documentation for the moonshotai/Kimi-K2-Instruct model by modifying its vllm serve launch command. The change introduces a new parameter, -dcp 8, which is then accompanied by updated benchmark results. This provides users with a clearer understanding of the recommended serving configuration and its performance implications.

Highlights

  • VLLM Serve Command Update: The vllm serve command for the moonshotai/Kimi-K2-Instruct model has been updated to include the -dcp 8 parameter, likely enabling distributed tensor parallelism with 8 devices.
  • New Benchmark Results: Corresponding benchmark results have been added to the documentation, showcasing the serving performance metrics (e.g., throughput, latency) after the inclusion of the -dcp 8 flag.
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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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.

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 updates the Kimi-K2 documentation by adding a -dcp 8 flag to a vllm serve command and including a new benchmark result. My review focuses on improving the clarity and consistency of the documentation. I've suggested explaining the new command-line flag and restructuring the new benchmark section to be more informative and consistent with the rest of the document.


# node 0:
vllm serve moonshotai/Kimi-K2-Instruct --trust-remote-code --tokenizer-mode auto --tensor-parallel-size 8 --pipeline-parallel-size 2 --dtype bfloat16 --quantization fp8 --max-model-len 2048 --max-num-seqs 1 --max-num-batched-tokens 1024 --enable-chunked-prefill --disable-log-requests --kv-cache-dtype fp8
vllm serve moonshotai/Kimi-K2-Instruct --trust-remote-code --tokenizer-mode auto --tensor-parallel-size 8 --pipeline-parallel-size 2 --dtype bfloat16 --quantization fp8 --max-model-len 2048 --max-num-seqs 1 --max-num-batched-tokens 1024 --enable-chunked-prefill --disable-log-requests --kv-cache-dtype fp8 -dcp 8
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The -dcp 8 parameter has been added to the command, but it's not a standard vllm argument and isn't explained in this document. To help users understand how to use this configuration, please add a description of what -dcp does to the "Key parameter notes" section.

Comment on lines +147 to 173
After adding '-dcp 8':
```bash
============ Serving Benchmark Result ============
Successful requests: 16
Request rate configured (RPS): 10000.00
Benchmark duration (s): 47.14
Total input tokens: 128000
Total generated tokens: 16000
Request throughput (req/s): 0.34
Output token throughput (tok/s): 339.38
Peak output token throughput (tok/s): 384.00
Peak concurrent requests: 16.00
Total Token throughput (tok/s): 3054.46
---------------Time to First Token----------------
Mean TTFT (ms): 2007.87
Median TTFT (ms): 1932.03
P99 TTFT (ms): 4680.76
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms): 45.01
Median TPOT (ms): 45.10
P99 TPOT (ms): 46.51
---------------Inter-token Latency----------------
Mean ITL (ms): 45.01
Median ITL (ms): 42.01
P99 ITL (ms): 52.01
==================================================
```
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Thank you for adding the benchmark results. To make this section clearer and more consistent with the rest of the document, please consider the following improvements:

  • Placement: The vllm serve command was updated for the 16xH800 setup, but this benchmark result is placed after the 16xH200 benchmark. Please move this section to follow the 16xH800 benchmark results for consistency.
  • Missing Command: For reproducibility, please include the vllm bench serve command that was used to generate these results.
  • Section Title: The title "After adding '-dcp 8':" could be more descriptive. Consider making it a sub-heading like #### With -dcp 8 under the appropriate benchmark section.
  • Code Block Language: This code block is marked as bash, while others are marked as shell. Using a consistent language specifier (shell or bash) would improve the document's consistency.
  • Final Newline: The file is missing a newline character at the end. It's a common convention to end files with a newline.

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.

1 participant