docs: migrate Profiler docs to three-tier structure#6003
Conversation
Create docs/components/profiler/ with: - README.md: Overview, feature matrix, quick start - profiler_guide.md: Detailed configuration and usage Add cross-references from existing profiling docs: - docs/benchmarks/sla_driven_profiling.md - docs/backends/sglang/profiling.md Add Profiler to Components section in index.rst navigation. Signed-off-by: Dan Gil <dagil@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
WalkthroughAdds a new Profiler component documentation (README and detailed guide), updates the site index to include the profiler, and inserts "See also" cross-reference notes into two existing docs. No code, API, or runtime behavior changes. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/ok to test 2a00679 |
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/components/profiler/README.md`:
- Around line 110-114: The fenced code block under "Example recommendations" is
missing a language tag (MD040); update the triple-backtick fence for that block
to include a language identifier (e.g., use ```text) so the block becomes a
labeled fenced code block, preserving the two recommendation lines inside (the
lines starting "Suggested prefill TP:4 ..." and "Suggested decode TP:4 ...").
Address CodeRabbit review: add text language identifier to Example recommendations code block (MD040). Signed-off-by: Dan Gil <dagil@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
/ok to test b25ed19 |
Expand profiler documentation by absorbing content from sla_driven_profiling.md and planner quickstart (non-destructive, originals kept): - profiler_guide.md: full config reference, profiling methods, DGDR workflow, parallelization sweep internals, troubleshooting - profiler_examples.md: complete DGDR YAMLs (dense, AIC, MoE, ConfigMap), WebUI usage, direct script examples - README.md: updated Next Steps and toctree Signed-off-by: Dan Gil <dagil@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
/ok to test b20506f |
- Add SPDX copyright headers to all 3 files (@Jont828) - Add supported systems comment to AIC example (@Jont828) - Use concrete disagg.yaml path in script example (@Jont828) - Clarify gpuType vs aicSystem distinction (@Jont828) - Add CLI-to-DGDR argument mapping note (@Jont828) - Clarify aicBackendVersion meaning with link (@Jont828) Signed-off-by: Dan Gil <dagil@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
/ok to test 5ff23d4 |
Co-authored-by: Jonathan Tong <jt572@cornell.edu> Signed-off-by: dagil-nvidia <dagil@nvidia.com>
|
/ok to test b0a107e |
|
^ My review comments are non-blocking btw. We can merge this asap to avoid too many rebase issues but figured it'd be good to have to follow up later. |
Signed-off-by: Dan Gil <dagil@nvidia.com> Signed-off-by: dagil-nvidia <dagil@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Jonathan Tong <jt572@cornell.edu>
Summary
docs/components/profiler/with Profiler component documentationTest plan
uv venv .venv-docs uv pip install --python .venv-docs --group docs uv run --python .venv-docs --no-project docs/generate_docs.py # Output: "build succeeded."Related
Part of docs hierarchy refactoring (Wave 1, PR 2).
Summary by CodeRabbit