|
||||||||
|
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/d/optout.
Hello.
I left the system run a couple days to capture the behavior.
OK. Our current situation is this: the system starts taking memory until 99% of it is consumed, and then keeps on working with 99% of memory consumed. From the 16752 Mb, ~16594 Mb are consumed.
Speed of the server is OK.
The GC pauses for minor collections keep on creeping up.
The following happened once: once the GC pauses got to ~3.7 seconds, the GUI stopped responding, although in the log the system was still responding (jobs being run, etc). I needed to restart the server (2 days ago).
I got an OOM message only once, when memory was 99% consumed: "java.lang.OutOfMemoryError: Requested array size exceeds VM limit". I haven't seen this anymore. The system continued working after this message.
I am not sure that this increase in memory usage is caused because of wrong GC values, but increases of memory used correspond with increases in minor collection times.
Sporadically I have ran the following commands to free memory:
echo 1 > /proc/sys/vm/drop_caches
free -m
echo 2 > /proc/sys/vm/drop_caches
free -m
echo 3 > /proc/sys/vm/drop_caches
free -m
sync
After these commands, I can see a clear diminution in memory usage, but the GC pause times keep on growing.