Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Attachments: thread_dump1.txt
Components: http_request
Created: 29/May/13 12:26 PM
Description:

We are running a set of Jenkins instances - 1 master and 8 slave nodes with version 1.505.
Recently decided to rather with to LTS releases and on 28th May we upgraded to 1.509.1
Unfortunately after the migration the UI of Jenkins became extremly slow - over 1 minute to get the page with the jobs (the "All" view contains 295 jobs at the moment).
We figured out that the pages where the number of shown jobs is smaller do load significantly faster, still much slower than before the upgrade (including the maintenance screens of the jobs and Jenkins itself).

We also doublechecked the load and on all nodes (master and slaves) it was <50% total CPU.

We did add the parameter mentioned in JENKINS-16474 --httpKeepAliveTimeout=1000 but it did not make any difference.

Eventually we did a simple test:

  • restart the master
  • open couple of browser windows navigating to main Jenkins page (with all jobs)
  • captured the thread-dump

The Thread-dump is attached. We noticed several blocked threads

"Handling GET /jenkins/ : RequestHandlerThread[#28]" Id=17767 Group=main BLOCKED on hudson.model.RunMap@733eeab4 owned by "Handling GET /jenkins/ : RequestHandlerThread[#33]" Id=17778

For us it looks like there is some severe issue with reading jobs configurations (perhaps from slave nodes) but for sure that's just a guess.


Also the startup time increased noticeably

  • 1.505 approx 1 minute
  • 1.509.1 over 10 minutes
Environment: Ubuntu 12.04.1 LTS
Project: Jenkins
Priority: Major Major
Reporter: Jaroslaw Swierk
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to