| Java Virtual Memory Usage at Eclipse startup [message #1746050] |
Thu, 20 October 2016 20:30  |
 Steven InAz
Messages: 7
Registered: September 2011 |
Junior Member |
|
|
The question I have has to do with the quantity of Virtual Memory eclipse requests at startup. I am running linux. When I take a look at "top" I see that the Java VM has requested 8G of virtual memory, and has 500k resident, an almost 20x discrepancy. This is for a stock installation of the C/C++ installation of Eclipse Neon 4.6.1, but is not specific to this Neon.
If I keep an eye on the memory usage while I am running having loaded a large project or two, I see the resident memory cap out at around 2.5G, with the virtual memory capping out around 11G, still a 4x being reserved over and above what is actually used.
Where I run into issues is when we have multiple users on a multi-core server with what should be near infinite memory. 10 users all running eclipse, has a virtual memory allocation space around 100G which makes it difficult to deploy eclipse in our current system.
The VM allocation is independent of the Eclipse.ini file (Xmx, Xmxs etc.) as covered by many other forums I have read, and verified by my own efforts to use them to tweak Eclipse at run time.
It looks like I am running Java 1.8.0_91, looks like Oracle.
Has anyone else run into the scalability issue I am describing? Were you able to do anything to fix it? I am hoping to find a VM / set of switches that is more of a lazy load.
|
|
|
| Re: Java Virtual Memory Usage at Eclipse startup [message #1746090 is a reply to message #1746050] |
Fri, 21 October 2016 13:28  |
Eric Rizzo
Messages: 3070
Registered: July 2009 |
Senior Member |
|
|
That's indeed very alarming, but it sounds to me more like a Java VM issue rather than Eclipse. Eclipse, being an ordinary resident of the JVM, can only affect the "internal" memory components it requests (heap, PermGen, etc) - basically, those things that are controlled by the options like Xmx, etc). Eclipse itself, as far as I know, has no say in how virtual memory is requested.
I know on Windows, where the JVM has had notoriously poor memory management, for example it requests a single contiguous block of memory based on the max heap size requested by the application, and that can cause problems because Windows fragments memory so much. But I've not heard of any memory allocation issues on linux.
Have you checked and general Java forums for JVM-related discussions about this?
|
|
|
|
|
| Re: Java Virtual Memory Usage at Eclipse startup [message #1746190 is a reply to message #1746188] |
Mon, 24 October 2016 19:59 |
Tauno Voipio
Messages: 742
Registered: August 2014 |
Senior Member |
|
|
I guess that you're running a 64 bit system.
Most of the space occupied at start seems to go to the various plug-ins. Is your Eclipse with all bells & whistles and a kitchen sink?
In my Kubuntu 14.04 LTS (32 bit), the space occupied by Eclipse is:
- Luna SR2: 299 Mbyte, 24 Mbyte shared,
- Neon.1: 333 Mbyte, 38 Mbyte shared.
The Java on the Luna installation is IcedTea 2.6.7, and on the Neon installation Java SE 1.8.0_60.
--
Tauno Voipio
|
|
|
Powered by
FUDForum. Page generated in 0.04019 seconds
] 
Search
Help
Register
Login
Home
