-
Bug
-
Resolution: Unresolved
-
Critical
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
Tested on a single core Windows 2008 R2 machine running Jenkins 1.596. The problem seems to get worse after installing the latest core (1.599 at this stage) due maybe to the latest log format changes
With multiple cores it might be possible to increase the number of rows to be shown without any issue...
[JENKINS-27001] On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze
Description |
Original:
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Tested on a single core Windows 2008 R2 machine... with multiple cores it *might* be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming |
New:
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Tested on a single core Windows 2008 R2 machine running Jenkins 1.596. The problem *seems* to get worse after installing the latest core (1.599) due maybe to the latest log format changes (?) With multiple cores it *might* be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming |
Description |
Original:
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Tested on a single core Windows 2008 R2 machine running Jenkins 1.596. The problem *seems* to get worse after installing the latest core (1.599) due maybe to the latest log format changes (?) With multiple cores it *might* be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming |
New:
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Tested on a single core Windows 2008 R2 machine running Jenkins 1.596. The problem *seems* to get worse after installing the latest core (1.599 at this stage) due maybe to the latest log format changes (?) With multiple cores it *might* be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming |
Description |
Original:
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Tested on a single core Windows 2008 R2 machine running Jenkins 1.596. The problem *seems* to get worse after installing the latest core (1.599 at this stage) due maybe to the latest log format changes (?) With multiple cores it *might* be possible to increase the number of rows to be shown without any issue. However, I think loading build logs at this stage is CPU consuming |
New:
On Windows installations if the pipeline view is set to show more than 200 jobs CPU is pushed to 100% causing the system to freeze Tested on a single core Windows 2008 R2 machine running Jenkins 1.596. The problem *seems* to get worse after installing the latest core (1.599 at this stage) due maybe to the latest log format changes (?) With multiple cores it *might* be possible to increase the number of rows to be shown without any issue... (?) |
Labels | Original: cpu pipeline | New: cpu |
Labels | Original: cpu | New: performance |
Workflow | Original: JNJira [ 161191 ] | New: JNJira + In-Review [ 180600 ] |
Then don't show all 200 jobs, you can limit the number of groups in pipeline configuration.