Page MenuHomePhabricator

In Phage, don't sit in a loop once we've read all messages from an agent
ClosedPublic

Authored by epriestley on Feb 19 2017, 3:04 PM.
Tags
None
Referenced Files
F19104214: D17387.id.diff
Fri, Dec 5, 1:04 PM
F19100103: D17387.diff
Thu, Dec 4, 10:16 PM
F19032119: D17387.diff
Tue, Nov 25, 4:29 AM
F19013896: D17387.diff
Sat, Nov 22, 5:45 PM
F19001612: D17387.diff
Fri, Nov 21, 3:47 AM
F18937901: D17387.diff
Nov 11 2025, 1:06 AM
F18858693: D17387.diff
Nov 1 2025, 10:45 PM
F18795972: D17387.id.diff
Oct 17 2025, 2:46 AM
Subscribers
None

Details

Summary

Ref T2794. The logic is intended to read "loop until we're done processing messages", but is currently missing a break;. This doesn't affect behavior yet, just makes us eat way too much CPU.

Test Plan

Saw time phage remote --hosts db001-16 status drop from 99% CPU time to <10%.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable