mirror of
https://we.phorge.it/source/phorge.git
synced 2024-11-23 07:12:41 +01:00
e9309fdd6a
Summary: Depends on D19751. Ref T13210. When Drydock needs to reclaim an existing unused resource in order to build a new resource to satisfy a lease, the lease which triggered the reclaim currently gets thrown back into the pool with a 15-second yield. If the queue is pretty empty and the reclaim is quick, this can mean that we spend up to 15 extra seconds just waiting for the lease update task to get another shot at building a resource (the resource reclaim may complete in a second or two, but nothing else happens until the yield ends). Instead, when a lease triggers a reclaim, have the reclaim reawaken the lease task when it completes. In the best case, this saves us 15 seconds of waiting. In other cases (the task already completed some other way, the resource gets claimed before the lease gets to it), it's harmless. Test Plan: - Allocated A, A, A working copies with limit 3. Leased a B working copy. - Before patch: allocation took ~32 seconds. - After patch: allocation takes ~17 seconds (i.e., about 15 seconds less). Reviewers: amckinley Reviewed By: amckinley Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam Maniphest Tasks: T13210 Differential Revision: https://secure.phabricator.com/D19752
2 lines
91 B
SQL
2 lines
91 B
SQL
UPDATE {$NAMESPACE}_drydock.drydock_command
|
|
SET properties = '{}' WHERE properties = '';
|