Add maximum task accounting
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | runqueue.py: Minor cleanup for RunQueueStats and userslib/ | +9 | 0 replies | |
| 2/2 | runqueue.py: Initial implementation of per task process limitslib/ | +21 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Add maximum task accounting
On my own machine, a 192 thread machine, if I start a new project without a local download cache, I end of DoSing my machine. I wanted a way to create a maximum number of tasks, of any given type, so that I could limit the number of concurrent do_fetch commands.
The first patch is a cleanup, while it's not required for the task accounting I did discover that a few operations were happening in the wrong order -- this could cause a problem if anyone is trying to use the RunQueueStats in new ways.
The second patch is the one that actually implements the max-task limits. As noted in the comment, while theoretically you could set this in a recipe, the behavior will be unpredictable, it's meant to be set in the global configuration space, i.e. the local.conf.
I've been using these patches successfully for the path few months.
Mark Hatle (2):
runqueue.py: Minor cleanup for RunQueueStats and users runqueue.py: Initial implementation of per task process limits
lib/bb/runqueue.py | 39 ++++++++++++++++++++++++++++++--------- 1 file changed, 30 insertions(+), 9 deletions(-)
Signature · 1 line
1.8.3.1