![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Ronen Peleg
|
|
Attachments:
|
Monitor_After_12_Hours.jpg, Monitor_After_1_Hour.jpg, Monitor_After_20_Hours.jpg, Monitor_After_23_Hours.JPG |
|
Components:
|
core |
|
Created:
|
17/Nov/13 10:18 AM
|
|
Description:
|
After Jenkins upgraded to LTS 1.509.4 from LTS 1.509.3 I notice that over time (24 hours) Jenkins becomes very slowly.
It turns out that Jenkins (under Jetty service) slowly "eats" the server memory. It's takes about 24 hours to take all the memory allocated to Jenkins (42GB). See the snapshots with examples...
1. Machine with Jetty up after restart.
2. Jenkins Used - After one Hour: 22GB
3. Jenkins Used - After 12 Hours: 27GB
4. Jenkins Used - After 20 Hours: 35GB
5. Jenkins Used - After 24 Hours: 39GB (Very slow)
Thanks,
Ronen.
|
|
Environment:
|
Linux Server with 24 CPUs and 64GB RAM
Jenkins version LTS 1.509.4 on Jetty
Memory allocated for Jenkins/Jetty process: 42GB
Jenkins working with 600 jobs
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Ronen Peleg
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
