AFAIK no. From my PoV it is not the biggest problem for JCasC performance. Currently it is rather a startup time. I am working on improving it in the background, and there have been also serious improvements last winter, thanks to Evaristo Gutiérrez <https://github.com/varyvol> and Francisco Fernández <https://github.com/fcojfernandez>. There are still a lot of tweaks we could apply.
On Tuesday, August 6, 2019 at 1:55:56 PM UTC+2, Florian Wilhelm wrote: > > > > On Tuesday, May 1, 2018 at 4:42:30 PM UTC+2, nicolas de loof wrote: >> >> >> >> 2018-05-01 14:59 GMT+02:00 Jesse Glick <[email protected]>: >> >>> On Sat, Apr 28, 2018 at 2:46 AM, nicolas de loof >>> <[email protected]> wrote: >> >> >> >>> > probably not such >>> > a trivial think to implement and alternative workflow executor to >>> replace >>> > CPS with a plain groovy runtime, is it ? >>> >>> Not trivial at all, but I believe feasible. >>> >> >> ok, then when this becomes available we would be able to make >> jenkinsfile-runner way simpler :D >> >> > > Im curious if anyone is working on that. Is there an issue for that in > Jira or something? I suspect this would make JFR run much faster as CPS > transformation has quite an impact on speed, right? > >> >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bf5cdf5e-9254-45e0-9ce6-bff43a0f2ef4%40googlegroups.com.
