-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Jenkins Administrator's Guide
By :

While Jenkins infrastructure best practices offer a distributed builds architecture11, Jenkins has only one controller to schedule work across agents. Because of this, as more agents and processes are connected to a controller, it can create CPU bottlenecks, disk I/O bottlenecks, and network I/O bottlenecks by agents provisioning and streaming data from builds. This section will explain the bottlenecks and share proposals for solving them in terms of the relationship between the controller and the agent. Topics in this section are also pretty well covered in the Jenkins World 2017 presentation by Jesse Glick: How to use Jenkins less12.
Agents can both download and upload a lot of data as part of normal operation: