facade: reduce pipeline preference log verbosity

[romange]

We should avoid logging VERY frequent events (potentially per request) as VLOG(1) as then we can not
use this logging level in prod.

[qodo-free-for-open-source-projects]

Code Review by Qodo

---

New Review Started

This review has been superseded by a new analysis

---

Powered by Qodo

[qodo-free-for-open-source-projects]

PR Summary by Qodo

facade: reduce pipeline preference log verbosity

✨ Enhancement 🕐 Less than 10 minutes

---

AI Description

• Reduce log verbosity when pipeline execution is preferred over admin queue.
• Keep diagnostic details available at higher VLOG level.

High-Level Assessment

The change is appropriately minimal: lowering the VLOG level preserves useful diagnostics while reducing default verbosity. No alternative approach is warranted for a one-line logging tweak.

Files changed (1) +1 / -1

Enhancement (1) +1 / -1

dragonfly_connection.ccLower VLOG level for pipeline-preference message +1/-1

Lower VLOG level for pipeline-preference message

• Changes the pipeline-preference log statement from VLOG(1) to VLOG(2) so it appears only at higher verbosity while retaining the same message content.

src/facade/dragonfly_connection.cc

[augmentcode]

🤖 Augment PR Summary

Summary: Reduces log noise for the pipeline-vs-admin-queue scheduling decision in Connection::AsyncFiber().

Changes: Raises the VLOG_IF level for the “Preferring pipeline execution…” message from 1 to 2 so it only appears with higher verbosity settings.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

---

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

---

Powered by Qodo