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
F15472469: D17387.id41807.diff
Sat, Apr 5, 1:54 PM
F15456324: D17387.id41810.diff
Sun, Mar 30, 8:42 AM
F15453825: D17387.id.diff
Sat, Mar 29, 2:41 PM
F15451898: D17387.diff
Sat, Mar 29, 12:26 AM
F15411546: D17387.diff
Wed, Mar 19, 9:26 AM
F15399595: D17387.id41810.diff
Mar 17 2025, 5:23 AM
F15393985: D17387.diff
Mar 15 2025, 11:18 PM
F15374776: D17387.diff
Mar 12 2025, 8:17 PM
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