Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

Thanks Marc , we will definitely update this settings and observe performance . For now below fix worked for me , not observing any issues recently with my application . 1.upgrade jdk8 version to recommended version (1.8.0_222-b10 and above) . 2.Install monitoring plugin in Jenkins. 3.Udat

Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

You might install the Jenkins Health Advisor by CloudBees and see if it has suggestions for your instance. It will check for conditions that have been found to cause problems in other installations and report them to you in a daily e-mail message. https://jenkins.io/blog/2019/11/22/jenkins-health

Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

We are using following JAVA_OPTS CONFIG in Jenkins deployment . "name": "JAVA_OPTS", "value": "-XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:+ParallelRefProcEnabled -XX:+UseStringDeduplication -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:+UnlockDiagnosticVMOptio

Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

Thanks Marc , We will check if it helps , Currently we have "maximum durability" settings configured now , we are planning to make it to "performance-optimized" . We have observed couple of time disc IO is very high sometimes . On Monday, January 20, 2020 at 5:54:38 AM UTC+5:30, Mark Waite

Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

I'm not aware of an open bug in Jenkins related to being slow over NFS, though Jenkins is quite disc intensive and runs best with local disc drives. You might refer to the following articles for more information: - Jenkins pipeline durability settings documentation

About Jenkins slowness for version 2.138 in multi branch pipeline project

Hi Team , We are using observing Jenkins slowness issues for jenkins version 2.138 in multi branch pipeline project . We have also used NFS 4.1 . After Jenkins restart it works for few days but at some stage it stuck and becomes unresponsive . As per observation only restart will solve this