Seems there has been some improvements in a new version of Jenkins. Much better, but not quite out of the woods yet. Upgrading to 2.181 seems to solve the slowness loading problem.
Let me repeat some of my comments from the Jenkins issue: https://issues.jenkins-ci.org/browse/JENKINS-56243 I have been trying Jenkins 2.181 on our Jenkins Test server. Really fast loading of UI, not seeing any slowness. Though the Jenkins Test server does not have as much build history, the real test would be to upgrade our Jenkins Production server. Opening a multibranch project branch, the page seems to have loaded completely, but loading is still ongoing for some more ~30 seconds. Looked at what was loading and seems to be prototype.js. There was an fix for this in JENKINS-49319, but it was reverted. Firefox is having much more problems than browsers with the Chromium engine. So it seems to be a javascript problem that last loading. What I find very odd. If I log in to Jenkins (using LDAP) all loading problems goes away. Why should logging in solve the loading slowness? The last remaining loading on Multibranch Pipeline branch project. Developer Tools in my browser showed me what was remaining trying to load. ajax 200 xhr prototype.js:1585 310 B 15 ms runs?since=%232&fullStages=true&_=1561103938220 200 xhr jquery2.js:998 48.8 KB 18 ms These two repeated several times for about 30+ seconds until the page was actually finished loading. onsdag 20. mars 2019 19.05.51 UTC+1 skrev Sverre Moe følgende: > > I did try to delete the cookies from Jenkins, and it became much faster at > loading. > > onsdag 20. mars 2019 15.22.52 UTC+1 skrev Sverre Moe følgende: >> >> I tried increasing the cache >> Size 50 >> TTL 1 hour >> >> Still loading is really slow for some. >> Refresh main page, fast. Then I try to enter a project. and I click and >> click and click, wait and wait, but nothing. Then it just loads after >> several seconds. >> >> onsdag 20. mars 2019 15.16.03 UTC+1 skrev Sverre Moe følgende: >>> >>> The LDAP caching is supposed to increase performance >>> >>> > Some LDAP servers may be slow, or rate limit client requests. In such >>> cases enabling caching may improve performance of Jenkins with the risk of >>> delayed propagation of user changes from LDAP and increased memory usage on >>> the master. >>> >>> onsdag 20. mars 2019 15.15.14 UTC+1 skrev Sverre Moe følgende: >>>> >>>> We have enabled cache for LDAP authentication >>>> Cache size 20 >>>> Cache TTL 5 min 0 sec >>>> >>>> >>>> Is there a workaround? Disabling cache perhaps? >>>> >>>> onsdag 20. mars 2019 00.03.01 UTC+1 skrev Stuart Rowe følgende: >>>>> >>>>> Since you have the Active Directory plugin installed, can you confirm >>>>> that you have caching enabled? We were bit by this when upgrading a test >>>>> instance to LTS 2.150.2. >>>>> See: https://issues.jenkins-ci.org/browse/JENKINS-56243 >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/09cd3897-a119-41ab-b5cd-f72f795a4137%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
