The first time we click on a link to see a build, the web UI hangs for
about ten minutes. stracing the thread that's got 100% of the cpu shows
that it's reading each one of the 500 junitResult.xml files:
...
open("/var/lib/jenkins/jobs/www/builds/42596/junitResult.xml", O_RDONLY) =
382
open("/var/lib/jenkins/jobs/www/builds/42595/build.xml", O_RDONLY) = 382
...
Each junitResult.xml file is about 17MB and takes about a second to load,
so the 500 files take almost ten minutes to load the page.
Any subsequent page loads for that particular build are immediate, and
jenkins doesn't go troll all the old junitResult.xml files. In fact loading
that build again even while the first one is still doing its thing is
immediate.
We're running v1.613. It seems like the change is recent-ish (last month
or two?) but we can't tie it to any particular change.
Has anyone else seen this? Any idea what might be going on?
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/f05f84c1-1c30-4145-b6e7-050b114850bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
