Skip to content

⚡ Bolt: [performance improvement] Disable synchronous stdout logging in YOLO inference#17

Draft
kingkillery wants to merge 1 commit into
mainfrom
bolt/optimization-yolo-inference-5044382922314046827
Draft

⚡ Bolt: [performance improvement] Disable synchronous stdout logging in YOLO inference#17
kingkillery wants to merge 1 commit into
mainfrom
bolt/optimization-yolo-inference-5044382922314046827

Conversation

@kingkillery
Copy link
Copy Markdown
Owner

@kingkillery kingkillery commented Apr 12, 2026

💡 What:
Added verbose=False to model.predict() calls in commonforms/inference.py.

🎯 Why:
By default, Ultralytics YOLO models log inference details (e.g., image size, bounding box coordinates, timings) to standard output for every single prediction. Synchronous logging to stdout creates blocking I/O overhead that accumulates, particularly when processing sequences of inputs (like document pages) inside loops.

📊 Impact:
Eliminates blocking I/O overhead during document processing, marginally speeding up throughput when predicting across multiple pages or running the CLI on large PDFs.

🔬 Measurement:
Run uv run pytest tests/inference_test.py to confirm the form extraction is completely unaffected and verify that extraneous stdout logging from the model no longer occurs.


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

Summary by CodeRabbit

  • Performance
    • Improved efficiency of inference operations during batch processing.

Add `verbose=False` to `model.predict()` calls in `commonforms/inference.py` to avoid synchronous stdout blocking overhead during inference loops.

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 12, 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: a34faa1c-8559-4540-a837-ac5869ef8747

📥 Commits

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

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

Walkthrough

This update disables synchronous verbose logging in YOLO inference calls by setting verbose=False on prediction methods. A learning note documents this optimization technique to reduce I/O blocking overhead during repeated predictions.

Changes

Cohort / File(s) Summary
YOLO Verbose Logging Configuration
.jules/bolt.md
New documentation file with learning note recommending verbose=False parameter in YOLO inference calls to eliminate stdout logging I/O overhead.
Inference Implementation
commonforms/inference.py
Updated YOLO.predict() calls in FFDNetDetector.extract_widgets to include verbose=False parameter on both ONNX and PyTorch prediction paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A speedy prediction we seek,
When verbose chatter makes logging weak,
False be the flag, and silent the call,
No blocking I/O—we inference them all!

🚥 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 clearly identifies the main change: disabling verbose output in YOLO inference for performance improvement, which matches the core objective of eliminating blocking I/O overhead from stdout logging.
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/optimization-yolo-inference-5044382922314046827

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