Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
Jenkins 2.263
pipelien-maven-plugin 3.9.3
PostgreSQL 9.5.23
Ubuntu 16.04.07 LTS
-
-
pipeline-maven-3.11.0
Description
We're facing a severe performance regression after upgrading the pipeline-maven-plugin from 3.8.3 to 3.9.3.
In 3.8.3 the downstreamPipelineTriggerRunListener needed ~52.031 ms to complete.
In 3.9.3 the downstreamPipelineTriggerRunListener needs ~24.694.245 ms (~7 hours)
The task manager shows 100% CPU usage for a postgre processes while the listener runs.
The only changes related to SQL-Statements between 3.8.3 and 3.9.3 have been introduced by this PR: https://github.com/jenkinsci/pipeline-maven-plugin/pull/226 (JENKINS-59500)
The second observation i made is that the message "Skip triggering ... because it has a dependency on a pipeline that will be triggered by this build" is now printed 46 times for the same job in 3.9.3 instead of 15 times in 3.8.3.
Attachments
Issue Links
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Description |
We're facing a severe performance refgression after upgrading the pipeline-maven-plugin from 3.8.3 to 3.9.0. In 3.8.3 the downstreamPipelineTriggerRunListener needed ~52.031 ms to complete. In 3.9.3 the downstreamPipelineTriggerRunListener needs ~24.694.245 ms (~7 hours) The task manager shows 100% CPU usage for a postgre processes while the listener runs. The only changes related to SQL-Statements between 3.8.3 and 3.9.3 i've found are related to this PR: https://github.com/jenkinsci/pipeline-maven-plugin/pull/226 ( The second observation i made is that the message "Skip triggering ... because it has a dependency on a pipeline that will be triggered by this build" is now printed 46 times for the same job in 3.9.3 instead of 15 times in 3.8.3. |
We're facing a severe performance regression after upgrading the pipeline-maven-plugin from 3.8.3 to 3.9.3. In 3.8.3 the downstreamPipelineTriggerRunListener needed ~52.031 ms to complete. In 3.9.3 the downstreamPipelineTriggerRunListener needs ~24.694.245 ms (~7 hours) The task manager shows 100% CPU usage for a postgre processes while the listener runs. The only changes related to SQL-Statements between 3.8.3 and 3.9.3 have been introduced by this PR: https://github.com/jenkinsci/pipeline-maven-plugin/pull/226 ( The second observation i made is that the message "Skip triggering ... because it has a dependency on a pipeline that will be triggered by this build" is now printed 46 times for the same job in 3.9.3 instead of 15 times in 3.8.3. |
Environment |
Jenkins 2.263 pipelien-maven-plugin 3.9.x PostgreSQL 9.5.23 Ubuntu 16.04.07 LTS |
Jenkins 2.263 pipelien-maven-plugin 3.9.3 PostgreSQL 9.5.23 Ubuntu 16.04.07 LTS |
Attachment | pipeline-maven.hpi [ 53926 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "Pull Request #323 (Web Link)" [ 26490 ] |
Attachment | logs.zip [ 53933 ] |
Attachment | pipeline-maven.hpi [ 53926 ] |
Attachment | pipeline-maven.hpi [ 53965 ] |
Attachment | logs-and-dumps_18-02-2018.zip [ 54023 ] |
Assignee | Benoit [ JIRAUSER133917 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Fixed but Unreleased [ 10203 ] |
Released As | pipeline-maven-3.11.0 |
Status | Fixed but Unreleased [ 10203 ] | Closed [ 6 ] |
I'm seeing this same behaviour. I have jobs that have finished their actual work (on other agents), but are now sat on master printing this message. CPU use is up at 100% on the master node. The jobs have been running for about 18 hours with no sign of stopping. The jobs cannot be cancelled, or at least the cancel request does nothing when made.
This issue also prevents the graceful update of the system with plugins or the next LTS release as when restarting via the web UI Jenkins will prefer to wait for all jobs to complete before restarting. It means I need to RDP onto my master node and shut Jenkins down using 'net stop'.