CI pipeline execution analysis
CI pipeline execution2/5 runs distributed across 7 agents
Agent utilization
Agent 0 / 2 tasks completed / 2m 04s active43%
Agent 5 / 6 tasks completed / 1m 41s active35%
Agent 1 / 2 tasks completed / 1m 07s active23%
Agent 7 / 1 tasks completed / 59s active20%
Agent 4 / 1 tasks completed / 57s active20%
Agent 3 / 3 tasks completed / 4s active1%
Agent 6 / 0 tasks completed
Improving agent utilization
An ideal agent utilization report will show even, high utilization across all agents. You might not see that for all distributed task executions though. For the most accurate assessment, watch how your agents perform on a CI pipeline execution where your entire project graph is affected (for example, after an NPM dependency is changed).
If you see low or uneven utilization across agents, here's some things you can try:
- Parallelize wherever you can
- Break apart projects with long-running targets, so their tasks can be more easily distributed across agents
- Break apart long-running targets such as e2e tests, so that they can run in parallel
Run durations
Improving run timings
Ideally you'd like to see all the runs in a CI pipeline execution happen in parallel. That may not be possible though, depending on how your tasks depend on one another. If you do see room for improvement, here's some things you can do to improve your run timings:
- Parallelize wherever you can