|Anonymous | Login | Signup for a new account||2019-09-15 11:46 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000386||YaCy||[All Projects] General||public||2014-03-07 21:50||2016-06-08 14:50|
|Platform||Linux||OS||Ubuntu||OS Version||14.04 beta|
|Target Version||Fixed in Version|
|Summary||0000386: Not working limiting the size of RAM.|
|Description||In the settings YaCy (admin console - basic configuration - performance - memory settings) i set limit the "Memory reserved for the JVM" in size 2000MB. But actually, the process uses is much more than 2000MB. Sometimes almost twice.|
|Steps To Reproduce||1. In the settings YaCy (admin console - basic configuration - performance - memory settings) i set limit the "Memory reserved for the JVM" in size 2000MB.|
2. Restart Yacy
3. After some time, check status memory through htop or ubuntu system monitor and see that it is more increased.
|Additional Information||the below screenshot shows statistics Htop|
|Tags||No tags attached.|
|Attached Files|| snapshot-2014-03-08-00-23-02.jpg [^] (20,253 bytes) 2014-03-07 21:50
snapshot-2014-03-08-00-24-54.jpg [^] (10,479 bytes) 2014-03-07 21:50
snapshot-2014-03-08-00-23-51.jpg [^] (9,472 bytes) 2014-03-07 21:51
memory.JPG [^] (54,374 bytes) 2016-06-08 14:50
the behavior you described looks ok to me.
You have a java process for YaCy that holds 6854M of virtual RAM, which doesn't need to be physical avalable. It is just a address-space to reach the index.
The Process holds 2261M reserved RAM, which is the real physical allocated RAM.
The Label 'Memory reserved for JVM' is not 100% correct. It means Heap-Memory for the JVM - because this is the parameter to configure on a JVM.
There are some other, smaler Memory-Types used by the JVM, that make the difference to your configured 2000M.
|Thank you for the clarification of the situation. No questions )|
however, there is the question: is it possible the release of the heap memory?
releasing Heap is not realypossible.
But You can try the following:
Shut down YaCy.
Open DATA/SETTINGS/yacy.conf in a text-editor.
Search for an entry of 'Xms' an change it to a lower value - maybe 1000m
Start YaCy again.
The Heap of a JVM has 2 parameters - Xmx (maximum Heap) and Xms (minimum Heap)
The Heap will start at a value of Xms an grow as needed up to Xms.
Usally it should also shrink if less Heap-Memory is needed, but shrinking does not work as fast as growing :-)
Using different values for Xms and Xmx has some cost in resources for this management - thats why it is not anabled by default.
Changing the 'Memory reserved for JVM' in the gui will overwrite Xms and Xmx to the new value.
|Thank you very much. Changed it to 1000. Look what will be the result. )|
Same discrepancy on Windows; however memory is reported differently:
Over 2GB physical RAM in use; JvmMx is configured at 800 in the service manager ( though that doesn't match "Memory reserved for JVM" which is set at 1024 - so I'm not sure which takes effect)
The missing 1GB seems is in "Working-set Shareable" which I believe is the executable and any libraries it uses in memory (eg. java)
|2014-03-07 21:50||Icewind1983||New Issue|
|2014-03-07 21:50||Icewind1983||File Added: snapshot-2014-03-08-00-23-02.jpg|
|2014-03-07 21:50||Icewind1983||File Added: snapshot-2014-03-08-00-24-54.jpg|
|2014-03-07 21:51||Icewind1983||File Added: snapshot-2014-03-08-00-23-51.jpg|
|2014-03-08 00:28||sixcooler||Note Added: 0000751|
|2014-03-08 00:42||Icewind1983||Note Added: 0000752|
|2014-03-08 01:00||Icewind1983||Note Added: 0000753|
|2014-03-08 01:32||sixcooler||Note Added: 0000754|
|2014-03-08 01:48||Icewind1983||Note Added: 0000755|
|2016-06-08 14:50||CGretski||Note Added: 0001246|
|2016-06-08 14:50||CGretski||File Added: memory.JPG|
|Copyright © 2000 - 2019 MantisBT Team|