-
Bug
-
Resolution: Unresolved
-
Major
Hi there!
We recently migrated from Jenkins core 2.46.3 with active choice plugin 1.5.3 to Jenkins core 2.107.2 with active choice plugin 2.1.
Before the update, our jobs were working fine, but since the update, the UI using this plugin has gone much much slower.
When Jenkins has just booted, it is pretty fast. However, the longer Jenkins has been running, the slower it gets (or so it seems). After a few days running, it takes from 10 to 30 minutes to display the arguments of a "build with parameters" page. We also observed a CPU peak on the Jenkins server during that time.
We tried reverting the active choice plugin to 2.0 and even 1.5.3 - still with Jenkins core 2.107.2 but this didn't help. This is why I suspect the problem comes from a compatibility with the Jenkins core.
In the specific job that is so slow, we use about 9 parameters. Among them 7 of them are or the type Active Choices Reactive Parameter. They are running scripts referencing the first two parameters.
In general, it is also not clear to me how this plugin works in terms of which parameter gets "resolved" first, when is which script called, etc.
- Is it also something other observe?
- Is there a work around?
- Is there some document about how the plugin works internally?
This issue has become a blocker for us, that's why I am happy to provide more details for troubleshooting and even to contribute to fixing the plugin if I am given some support.
By the way, there's definitely a few issues, but this plugin is awesome! Thanks to all the contributors.
Cheers,
Thanks for reporting the bug bernard87.
Some days ago I worked on an issue that could be related to this one https://issues.jenkins-ci.org/browse/JENKINS-39593
I do not have an instance of Jenkins with enough jobs and builds to reproduce the slowness. That's my main challenge when working on these two issues.
What would be grand, is if someone could help by providing a simple case to reproduce the slowness. Something like "with this 2 jobs, everything works OK, but if you do this and that, then you will notice that the performance has downgraded significantly etc etc".
Having a single job that shows the slowness, and perhaps its config.xml attached here, would be helpful. Or any other thing that you can think that could be helpful.
First step will be to make sure whether it's a JS, Java, or JS+Java issue. Then investigate whether it was a change from 1.4 -> 2.x, or if something changed in Jenkins. I can spare some hours every month for the Active Choice, but pull requests, code review, etc, more than welcome (:
Cheers
Bruno