Skip to content

⚡ Bolt: Disable synchronous stdout blocking in YOLO inference#24

Draft
kingkillery wants to merge 1 commit into
mainfrom
bolt-disable-yolo-verbose-2208654794495151207
Draft

⚡ Bolt: Disable synchronous stdout blocking in YOLO inference#24
kingkillery wants to merge 1 commit into
mainfrom
bolt-disable-yolo-verbose-2208654794495151207

Conversation

@kingkillery
Copy link
Copy Markdown
Owner

@kingkillery kingkillery commented Apr 16, 2026

💡 What: Added verbose=False to the Ultralytics YOLO model.predict() calls in extract_widgets.
🎯 Why: By default, Ultralytics YOLO logs verbose output (e.g. image size, inference time, detected classes) to stdout for every prediction. When predicting across multiple pages or running in a tight loop, this synchronous I/O blocks the main thread and introduces unnecessary overhead.
📊 Impact: Reduces inference time overhead by avoiding synchronous console writes, which translates to a measurable improvement in overall PDF processing speed, especially on multi-page documents or in high-throughput environments.
🔬 Measurement: Can be verified by running PDF extraction with a large document. The console output should no longer spam YOLO prediction logs, and the overall execution time will be reduced compared to the unoptimized version.


PR created automatically by Jules for task 2208654794495151207 started by @kingkillery

Summary by CodeRabbit

  • Documentation

    • Added documentation about inference performance optimization considerations.
  • Chores

    • Improved inference efficiency by reducing default logging overhead in model prediction calls.

…/O overhead

Co-authored-by: kingkillery <200727508+kingkillery@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4294330a-d8fe-448c-b1c2-fdd0c7b9b002

📥 Commits

Reviewing files that changed from the base of the PR and between e00f2d1 and c4b77cf.

📒 Files selected for processing (2)
  • .jules/bolt.md
  • commonforms/inference.py

Walkthrough

A documentation entry records a YOLO logging optimization technique, and the same optimization is applied to the inference module by passing verbose=False to model prediction calls to reduce console logging overhead.

Changes

Cohort / File(s) Summary
Documentation
.jules/bolt.md
Added learning note about Ultralytics YOLO's verbose output behavior and recommended mitigation strategy for production environments.
Inference Optimization
commonforms/inference.py
Applied verbose=False parameter to model.predict() calls in both ONNX and PT inference paths within FFDNetDetector.extract_widgets().

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit hops through silent streams,
No verbose logs in production dreams,
With verbose=False, the noise is gone,
Performance blooms when chattiness is shone!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately identifies the main change: disabling verbose output in YOLO inference to prevent stdout blocking, which aligns with the core modifications in both the documentation and code changes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bolt-disable-yolo-verbose-2208654794495151207

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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