Skip to content

Conversation

QiJune
Copy link
Collaborator

@QiJune QiJune commented Jul 22, 2025

There is already a check inside the while loop:

                new_requests = self._fetch_new_requests()
                if self.should_stop_processing:
                    break

Summary by CodeRabbit

  • Refactor
    • Updated internal processing loops to improve clarity and consistency. No changes to user-facing features or behavior.

@QiJune QiJune requested a review from a team as a code owner July 22, 2025 02:43
@QiJune QiJune requested a review from shaharmor98 July 22, 2025 02:43
Copy link
Contributor

coderabbitai bot commented Jul 22, 2025

Walkthrough

The update modifies three executor loop methods by changing their loop conditions from while not self.should_stop_processing: to while True:, moving the exit check inside the loop body with an if self.should_stop_processing: break statement. No other logic or control flow was altered.

Changes

File(s) Change Summary
tensorrt_llm/_torch/pyexecutor/py_executor.py Updated three executor loop methods to use while True: with an internal break condition based on self.should_stop_processing.

Estimated code review effort

1 (~2 minutes)

Poem

In the loops we hop anew,
Gone is the old condition's view.
Now we spin in endless cheer,
Until a signal says "break here!"
Rabbits love a tidy loop—
Hop, hop, stop, and then regroup! 🐇

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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 docstrings to generate docstrings for this 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

♻️ Duplicate comments (2)
tensorrt_llm/_torch/pyexecutor/py_executor.py (2)

814-821: Same late-exit pattern as above

The _executor_loop body repeats the “do work → then break” sequence. Refactor here as well to avoid the extra _fetch_new_requests() after shutdown.


958-965: Ditto for overlap loop

For consistency and to prevent any accidental blocking, apply the pre-check arrangement in _executor_loop_overlap too.

🧹 Nitpick comments (1)
tensorrt_llm/_torch/pyexecutor/py_executor.py (1)

656-663: Loop now runs one extra bookkeeping step after shutdown – double-check queue blocking behaviour

Switching to while True: makes the loop enter once even when should_stop_processing is already True.
Normally this is harmless, but _fetch_new_requests() might:

  1. Touch CUDA / NCCL state (extra work), and
  2. Potentially block on the request queue (implementation-dependent).

If the queue’s fetch_new_requests() performs a blocking get() with no timeout, the executor could hang on the final iteration.

Consider guarding the expensive / blocking part first:

 while True:
-    profile_step()
-    if self.enable_iter_perf_stats:
-        iter_start_time = time.time()
-    new_requests = self._fetch_new_requests()
-    if self.should_stop_processing:
-        break
+    if self.should_stop_processing:
+        break
+    profile_step()
+    if self.enable_iter_perf_stats:
+        iter_start_time = time.time()
+    new_requests = self._fetch_new_requests()

Same pattern applies to the other executor loops.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fddb7f1 and 0ff85d0.

📒 Files selected for processing (1)
  • tensorrt_llm/_torch/pyexecutor/py_executor.py (3 hunks)
🧠 Learnings (1)
tensorrt_llm/_torch/pyexecutor/py_executor.py (1)

Learnt from: amitz-nv
PR: #5616
File: tensorrt_llm/executor/worker.py:375-384
Timestamp: 2025-07-17T09:01:27.374Z
Learning: In tensorrt_llm/executor/worker.py, the LoRA adapter cache optimization logic that checks is_adapter_in_cpu_cache() and conditionally passes None for weights/config has a known race condition issue that cannot be solved with simple error handling or verification checks. This is a known limitation that requires a more comprehensive solution.

🧰 Additional context used
🧠 Learnings (1)
tensorrt_llm/_torch/pyexecutor/py_executor.py (1)

Learnt from: amitz-nv
PR: #5616
File: tensorrt_llm/executor/worker.py:375-384
Timestamp: 2025-07-17T09:01:27.374Z
Learning: In tensorrt_llm/executor/worker.py, the LoRA adapter cache optimization logic that checks is_adapter_in_cpu_cache() and conditionally passes None for weights/config has a known race condition issue that cannot be solved with simple error handling or verification checks. This is a known limitation that requires a more comprehensive solution.

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 22, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12510 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12510 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9297 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 22, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12522 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12522 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9308 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 22, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12556 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12556 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9337 completed with status: 'FAILURE'

@QiJune
Copy link
Collaborator Author

QiJune commented Jul 22, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12569 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12569 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9348 completed with status: 'SUCCESS'

@QiJune QiJune changed the title Chore: remove duplicate should_stop_processing check chore: remove duplicate should_stop_processing check Jul 23, 2025
@QiJune QiJune merged commit a8253b9 into NVIDIA:main Jul 23, 2025
3 checks passed
NVShreyas pushed a commit to NVShreyas/TensorRT-LLM that referenced this pull request Jul 28, 2025
Ransiki pushed a commit to Ransiki/TensorRT-LLM that referenced this pull request Jul 29, 2025
lancelly pushed a commit to lancelly/TensorRT-LLM that referenced this pull request Aug 6, 2025
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.

4 participants