[JIRA] (JENKINS-59311) Poor performance when using 'grep'

Change By:	Christoph Fetzer
Summary:	Poor performance of pipeline build compared to freestyle when using 'grep'

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

ch.fetzer@gmx.net (JIRA)

unread,

Oct 10, 2019, 5:44:03 AM10/10/19

to jenkinsc...@googlegroups.com

Christoph Fetzer edited a comment on

This jenkins installation is driving me nuts - the slow behaviour came back.

The last quick run was on September, 27th. After that the build failed for some days due to issues with the code and the libraries used. The first completing build after that on Oct. 9th was slow again (same times - ~45min vs 3:40hours).

OK, I noticed, there are failed builds with indicatino of slow behaviour since October, 2nd. The builds before failed after only 6mins.

I implemented every updates in that time as soon as I realised them. There were a number of them in that time frame. Is there a log that shows the plugins updated and the version change? With that I could restore the state of September 27th and apply all the updates step by step until the build gets slower again.

ch.fetzer@gmx.net (JIRA)

unread,

Oct 10, 2019, 5:45:02 AM10/10/19

to jenkinsc...@googlegroups.com

Christoph Fetzer updated an issue

Jenkins /

Change By:	Christoph Fetzer
Environment:	jenkins ver 2.176.3 jenkins ver 2.190.1

ch.fetzer@gmx.net (JIRA)

unread,

Oct 18, 2019, 3:01:02 AM10/18/19

to jenkinsc...@googlegroups.com

Christoph Fetzer commented on

The speed decrease dissappeared again.

Maybe it got lost a little through the history of all the comments:

the decrease happens only in one step, not distributed over all
in case it runs slowly, removing a '| grep' from a makefile build rule immediately takes down the speed decrease

I now started tracking all the plugin updates to maybe get a correlation between jenkins updates and speed impact

ch.fetzer@gmx.net (JIRA)

unread,

Nov 12, 2019, 3:20:03 AM11/12/19

to jenkinsc...@googlegroups.com

Christoph Fetzer commented on

A new finding:

for a lot of sequential updates I aborted the running job after recognizing the build speed. That caused hanging processes in the back that made cleaning the workplace impossible. To recover from that I rebooted the machine (without having applied an update). After that the build ran slowly again.

In the meantime the build got a little faste, it 'only' takes 5 hours instead of 8 previously. I can't find out the real time since when it happened because I had a number of failing builds in that time.

ch.fetzer@gmx.net (JIRA)

unread,

Nov 14, 2019, 9:56:03 AM11/14/19

to jenkinsc...@googlegroups.com

Christoph Fetzer commented on

Arg - this issue doesn't like being chased.

Every time I do a single action like update, reboot or restart behaviour stays the same.

Whenever I do simultaneous actions, something changes.

This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again.

ch.fetzer@gmx.net (JIRA)

unread,

Nov 14, 2019, 9:59:03 AM11/14/19

to jenkinsc...@googlegroups.com

Christoph Fetzer edited a comment on

Arg - this issue doesn't like being chased.

Every time I do a single action like update, reboot or restart behaviour stays the same.

Whenever I do simultaneous actions, something changes.

This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again.

BTW: really no support here? Where else can I get assistance?

ch.fetzer@gmx.net (JIRA)

unread,

Nov 14, 2019, 11:01:02 AM11/14/19

to jenkinsc...@googlegroups.com

Christoph Fetzer edited a comment on

Arg - this issue doesn't like being chased.

Every time I do a single action like update, reboot or restart behaviour stays the same.

Whenever I do simultaneous actions, something changes.

This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again.

Noticeable: I restarted jenkins by starting and stopping the jenkins service this time.

BTW: really no support here? Where else can I get assistance?

ch.fetzer@gmx.net (JIRA)

unread,

Nov 25, 2019, 4:27:02 AM11/25/19

to jenkinsc...@googlegroups.com

Christoph Fetzer commented on

After the latest updates I got the problem again. Besides, all my automatic build weren't restartet....

The list of updates:

Jira 3.0.10 -> 3.0.11
Oracle Java SE Development Kit Installer 1.3->1.4
Script Security 1.67->1.68
Warnings Next Generation 7.2.0->7.2.1

Jenkins v2.190.3

Lat*'s see what happens after a service restart...

ch.fetzer@gmx.net (JIRA)

unread,

Nov 25, 2019, 4:28:03 AM11/25/19

to jenkinsc...@googlegroups.com

Christoph Fetzer updated an issue

Jenkins /

Change By:	Christoph Fetzer
Environment:

jenkins ver 2.176.3
jenkins ver 2.190.1

jenkins ver 2.190.3

ch.fetzer@gmx.net (JIRA)

unread,

Nov 25, 2019, 4:32:02 AM11/25/19

to jenkinsc...@googlegroups.com

Christoph Fetzer updated an issue

Jenkins /

Change By:	Christoph Fetzer
Component/s:	core
Component/s:	pipeline

ch.fetzer@gmx.net (JIRA)

unread,

Nov 25, 2019, 6:34:02 AM11/25/19

to jenkinsc...@googlegroups.com

Christoph Fetzer edited a comment on