Hi,
I have Jenkins master (v2.190.1) installed as EC2 t2.small - it worked as expected until i've updated plugins recently and restarted jenkins.
Now i can see that jenkins process consumes 100% CPU and it's caused by IOwait - disk performance is a bottleneck.
Jenkins started to do some heavy disk reading which caused running out for EBS burst balance - now with 150G EBS i should have around 450 IOPS and it seems not to be enough for Jenkins - but it worked just fine a week ago.
When i track jenkins process with strace i see that it reads/scans every job and branch and build i have which probably is the source of the issue. How can i check which plugin caused or maybe is it desired behavior that after restart Jenkins scan all the files over and over again?