Skip to content

Conversation

@faradawn
Copy link
Contributor

@faradawn faradawn commented May 31, 2025

Overview:

Adds 4 images to the front page. Let me know which one to remove or edit.

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

  • closes GitHub issue: #xxx

Summary by CodeRabbit

  • Documentation
    • Enhanced the README with a banner image and new sections illustrating GPU evolution and multi-node, multi-GPU setups.
    • Added explanatory content introducing NVIDIA Dynamo and its architecture.
    • Improved formatting for better clarity and visual presentation.

@copy-pr-bot
Copy link

copy-pr-bot bot commented May 31, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions
Copy link

👋 Hi faradawn! Thank you for contributing to ai-dynamo/dynamo.

Just a reminder: The NVIDIA Test Github Validation CI runs an essential subset of the testing framework to quickly catch errors.Your PR reviewers may elect to test the changes comprehensively before approving your changes.

🚀

@github-actions github-actions bot added external-contribution Pull request is from an external contributor docs labels May 31, 2025
@pull-request-size pull-request-size bot added size/S and removed size/XS labels Jun 1, 2025
@faradawn faradawn marked this pull request as ready for review June 2, 2025 01:59
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 2, 2025

Walkthrough

The README.md file was updated by replacing the top-level heading with a banner image and adding a new section titled "The Era of Multi-Node, Multi-GPU" featuring images and explanatory text about GPU scaling challenges. An "Introducing NVIDIA Dynamo" heading and architecture diagram were also added, along with minor formatting changes. No code or technical instructions were altered.

Changes

File(s) Change Summary
README.md Replaced top heading with banner image; added "The Era of Multi-Node, Multi-GPU" section with images and explanatory text; inserted "Introducing NVIDIA Dynamo" heading and architecture diagram; minor formatting adjustments; no technical content changed.

Poem

In README fields where banners gleam,
New diagrams and visions stream.
GPUs and nodes, in rows they stand,
Dynamo guides with steady hand.
A rabbit grins at what’s in store—
Clearer docs and images galore!
🐇✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
README.md (4)

28-28: Section heading style consistency
### The Era of Multi-Node, Multi-GPU is valid Markdown, but markdownlint flagged a preference for closed ATX headings (### Title ###). Confirm your repository’s heading style guide and update if needed.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


33-33: Refine wording for precision
Consider avoiding the overused word “exactly.” For example:

- This orchestration gap is exactly what NVIDIA Dynamo is built to close.
+ This orchestration gap is precisely what NVIDIA Dynamo is built to close.
🧰 Tools
🪛 LanguageTool

[style] ~33-~33: Consider an alternative for the overused word “exactly”.
Context: ... accelerator? This orchestration gap is exactly what NVIDIA Dynamo is built to close. ...

(EXACTLY_PRECISELY)


35-35: Fix typo in alt text
The alt text reads “Multi Node Nulti GPU” but should be “Multi Node Multi GPU” for clarity and accessibility:

- ![Multi Node Nulti GPU](./docs/images/frontpage-gpu-vertical.png)
+ ![Multi Node Multi GPU](./docs/images/frontpage-gpu-vertical.png)

39-39: Introducing section heading style
The new ### Introducing NVIDIA Dynamo heading follows the same style as above. If you choose closed ATX (### Title ###), update this as well; otherwise it’s fine as-is.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

39-39: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 859944f and b38d50e.

⛔ Files ignored due to path filters (4)
  • docs/images/frontpage-architecture.png is excluded by !**/*.png
  • docs/images/frontpage-banner.png is excluded by !**/*.png
  • docs/images/frontpage-gpu-evolution.png is excluded by !**/*.png
  • docs/images/frontpage-gpu-vertical.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • README.md (3 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[style] ~33-~33: Consider an alternative for the overused word “exactly”.
Context: ... accelerator? This orchestration gap is exactly what NVIDIA Dynamo is built to close. ...

(EXACTLY_PRECISELY)

🪛 markdownlint-cli2 (0.17.2)
README.md

28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


39-39: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build and Test - vllm
🔇 Additional comments (3)
README.md (3)

17-17: Add banner image for front page
The banner provides a welcoming visual introduction. Ensure the relative path ./docs/images/frontpage-banner.png resolves correctly on GitHub (the leading ./ is valid but optional).


30-30: GPU evolution illustration added
Great visual to highlight the memory/compute growth challenge. The alt text “GPU Evolution” is concise and descriptive.


43-43: Add architecture overview diagram
The diagram enriches the README. Current alt text “Dynamo architecture” is sufficient, though you might consider “Architecture diagram of NVIDIA Dynamo” for extra descriptiveness.

@ishandhanani
Copy link
Contributor

This looks really great! I'll leave it to @nnshah1 to review the images. Maybe we can use some from some of our official slides.

@faradawn
Copy link
Contributor Author

faradawn commented Jun 2, 2025

Thank you @ishandhanani for the quick review! Let me know if there is anything I can add.

@faradawn
Copy link
Contributor Author

faradawn commented Jun 4, 2025

Hi @nnshah1 , I updated the branch and plan to merge. Let me know if any issue comes up and I can keep updating the guide,

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🔭 Outside diff range comments (1)
README.md (1)

17-43: 💡 Verification agent

🧩 Analysis chain

Verify image paths and file sizes

Ensure all new images exist under docs/images/ and are reasonably optimized for web (e.g., compressed PNGs under 200 KB).


🏁 Script executed:

#!/bin/bash
# List the added frontpage images and their sizes
fd -e png docs/images/frontpage-*.png --exec ls -lh {}

Length of output: 472


We need to correctly locate and list those frontpage images. Let’s try this instead:


🏁 Script executed:

#!/bin/bash
# List all frontpage PNGs under docs/images and show their sizes
fd --type f -e png 'frontpage-.*\.png' docs/images --exec ls -lh {} \;

Length of output: 420


Optimize frontpage-banner.png size

All frontpage images exist under docs/images/. Three of them meet the <200 KB guideline:

  • docs/images/frontpage-architecture.png – 89 KB
  • docs/images/frontpage-gpu-vertical.png – 151 KB
  • docs/images/frontpage-gpu-evolution.png – 86 KB

However, docs/images/frontpage-banner.png is 1.7 MB (>200 KB). Please compress or convert it to a more web-friendly format to improve load times.

🧰 Tools
🪛 LanguageTool

[style] ~33-~33: Consider an alternative for the overused word “exactly”.
Context: ... accelerator? This orchestration gap is exactly what NVIDIA Dynamo is built to close. ...

(EXACTLY_PRECISELY)


[uncategorized] ~41-~41: Possible missing comma found.
Context: ... NVIDIA Dynamo NVIDIA Dynamo is a high-throughput low-latency inference framework designe...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)

25-25: Spaces inside link text
null

(MD039, no-space-in-links)


28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


39-39: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)

🧹 Nitpick comments (3)
README.md (3)

17-17: Add more descriptive alt text for the banner image

The current alt text "Dynamo banner" is very generic. For accessibility, consider something like:

![NVIDIA Dynamo frontpage banner](./docs/images/frontpage-banner.png)

28-30: Consolidate or prune redundant GPU visuals

You’ve introduced two GPU-focused graphics (GPU Evolution and Multi Node GPU) back-to-back. To reduce visual redundancy and sharpen your narrative, consider removing or merging one of them.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


39-43: Improve alt text for the architecture diagram

The alt text "Dynamo architecture" is minimal. For clarity, consider a more descriptive caption such as:

![High-level architecture of NVIDIA Dynamo](./docs/images/frontpage-architecture.png)
🧰 Tools
🪛 LanguageTool

[uncategorized] ~41-~41: Possible missing comma found.
Context: ... NVIDIA Dynamo NVIDIA Dynamo is a high-throughput low-latency inference framework designe...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)

39-39: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b38d50e and d5743a8.

📒 Files selected for processing (1)
  • README.md (3 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[style] ~33-~33: Consider an alternative for the overused word “exactly”.
Context: ... accelerator? This orchestration gap is exactly what NVIDIA Dynamo is built to close. ...

(EXACTLY_PRECISELY)


[uncategorized] ~41-~41: Possible missing comma found.
Context: ... NVIDIA Dynamo NVIDIA Dynamo is a high-throughput low-latency inference framework designe...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)
README.md

28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


39-39: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build and Test - vllm

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Signed-off-by: Faradawn Yang <[email protected]>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
README.md (4)

17-17: Improve image alt text for accessibility

The alt text "Dynamo banner" is quite generic. Consider making it more descriptive (e.g., "NVIDIA Dynamo frontpage banner") to better support screen reader users.


28-28: Align ATX heading style

### The Era of Multi-Node, Multi-GPU currently lacks closing hashes and triggers MD003. You can either close it as ### The Era of Multi-Node, Multi-GPU ### or adjust the linter rules to accept unclosed headings.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


30-30: Enhance alt text for clarity

The alt text "GPU Evolution" is a bit terse. A more descriptive alt text—such as "Diagram showing GPU evolution across generations"—would improve context for assistive technologies.


43-43: Enrich architecture diagram alt text

The alt text "Dynamo architecture" could be more illustrative. For example, "Diagram of NVIDIA Dynamo multi-node architecture" would give users better context.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d5743a8 and 58ace97.

📒 Files selected for processing (1)
  • README.md (3 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[style] ~33-~33: Consider an alternative for the overused word “exactly”.
Context: ... accelerator? This orchestration gap is exactly what NVIDIA Dynamo is built to close. ...

(EXACTLY_PRECISELY)


[uncategorized] ~41-~41: Possible missing comma found.
Context: ... NVIDIA Dynamo NVIDIA Dynamo is a high-throughput low-latency inference framework designe...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)
README.md

28-28: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)


39-39: Heading style
Expected: atx_closed; Actual: atx

(MD003, heading-style)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build and Test - vllm
🔇 Additional comments (1)
README.md (1)

35-35: LGTM

The alt text "Multi Node Multi-GPU topology" and image path are clear and correctly formatted.

@faradawn faradawn requested a review from ishandhanani June 5, 2025 22:23
@faradawn
Copy link
Contributor Author

faradawn commented Jun 5, 2025

Hi @ishandhanani I sync'ed to the main branch and all the images render correctly. Could you help merge, as I couldn't find the merge button. Thanks!

@harryskim
Copy link
Contributor

I think we should add. Want me to approve @ishandhanani ?

@nnshah1 nnshah1 requested a review from harryskim June 8, 2025 23:40
@harryskim harryskim merged commit 98708c4 into ai-dynamo:main Jun 8, 2025
8 checks passed
@faradawn
Copy link
Contributor Author

faradawn commented Jun 9, 2025

Thank you @harryskim for checking and merging! Love to keep improving the readme and docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs external-contribution Pull request is from an external contributor size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants