| How do I reduce the size of Eclipse 3.2 memory footprint? [message #252002] |
Tue, 11 March 2008 15:40  |
Eclipse User |
|
|
|
Originally posted by: kwarner.uneedspeed.net
Environment: Win2k SP4; Java 1.5.0.9; 512meg memory;
As you see, I have an old slow, tiny machine. Running Eclipse 3.2
sometimes I run out of memory for my applet/apps.
Two questions:
1) How do I increase the memory available to run Eclipse?
I know how to set the JVM parameters to set the memory limits
for my applets/apps. But I have only a limited amount of physical
memory. But I don't know how to give Eclipse more memory or if
that is even necessary.
2) How do I reduce the overall size of the memory footprint of Eclipse?
For example: When I installed Eclipse 3.2 it came with SQL Development; Team;
Web and XML; Web Services; XDoclet; Plug-in Development; Report Design; Model Validation; Agent Controller; etc.
I don't even know what some of those things are and I never use any of them.
So why should I even load them?
So the question is: how do I uninstall that stuff and will it give me a smaller
memory footprint to do so?
And then, how would I increase the memory available to run Eclipse?
|
|
|
| Re: How do I reduce the size of Eclipse 3.2 memory footprint? [message #252008 is a reply to message #252002] |
Tue, 11 March 2008 18:29  |
| Eclipse User |
|
|
|
Originally posted by: groups.pellaton.li
Hi
Eclipse does not load all installed plug-ins (osgi bundles) during the
startup. Bundles are loaded when needed - either by a user action (like
opening a view or firing a command) or as a dependency of another bundle
that needs to be started (aka lazy loading). This behaviour can be
observed using JConsole in combination with the osgi-console.
Don't worry about too many installed features; as long as you don't use
them they don't affect the memory footprint. The possibly easiest way to
reduce the amount of installed (not loaded) features is downloading the
bare Eclipse SDK instead of a "bloated" all-in-one package.
JVM parameters are the way to assign memory to Eclipse. All parameters
(Xmx, Xms, XX:PermGen, ...) work as expected. Again, the JConsole of the
JDK is a great tool for hunting memory issues as it offers graphical
monitoring of the different JVM memory areas and sizes and their usage.
I must admit depending on what features you plan to use and the size of
your projects, it will be tough finding good settings with 512MB of
physical RAM, especially as Windows already occupies quite a lot of it.
HTH
Michael
DemonDuck wrote:
> Environment: Win2k SP4; Java 1.5.0.9; 512meg memory;
>
> As you see, I have an old slow, tiny machine. Running Eclipse 3.2
> sometimes I run out of memory for my applet/apps.
>
> Two questions:
>
> 1) How do I increase the memory available to run Eclipse?
>
> I know how to set the JVM parameters to set the memory limits
> for my applets/apps. But I have only a limited amount of physical
> memory. But I don't know how to give Eclipse more memory or if
> that is even necessary.
>
> 2) How do I reduce the overall size of the memory footprint of Eclipse?
>
> For example: When I installed Eclipse 3.2 it came with SQL Development; Team;
> Web and XML; Web Services; XDoclet; Plug-in Development; Report Design; Model Validation; Agent Controller; etc.
>
> I don't even know what some of those things are and I never use any of them.
> So why should I even load them?
>
> So the question is: how do I uninstall that stuff and will it give me a smaller
> memory footprint to do so?
>
> And then, how would I increase the memory available to run Eclipse?
|
|
|
| Re: How do I reduce the size of Eclipse 3.2 memory footprint? [message #252012 is a reply to message #252008] |
Tue, 11 March 2008 19:46 |
| Eclipse User |
|
|
|
Originally posted by: kwarner.uneedspeed.net
Thanks Michael,
I needed a jump start for my memory. I get to doing things a certain way
and forget all the other details ...
Michael Pellaton wrote:
> Hi
>
> Eclipse does not load all installed plug-ins (osgi bundles) during the
> startup. Bundles are loaded when needed
[stuff deleted]
I forgot then remembered that the way to set memory params is in eclipse.bat
> JVM parameters are the way to assign memory to Eclipse. All parameters
> (Xmx, Xms, XX:PermGen, ...) work as expected.
I've never used JConsole and now I must ask -- how do I do that in Eclipse?
Again, the JConsole of the
> JDK is a great tool for hunting memory issues as it offers graphical
> monitoring of the different JVM memory areas and sizes and their usage.
>
Tell me about it :-(
> I must admit depending on what features you plan to use and the size of
> your projects, it will be tough finding good settings with 512MB of
> physical RAM, especially as Windows already occupies quite a lot of it.
>
> HTH
>
> Michael
>
> DemonDuck wrote:
>
>>Environment: Win2k SP4; Java 1.5.0.9; 512meg memory;
>>
>>As you see, I have an old slow, tiny machine. Running Eclipse 3.2
>>sometimes I run out of memory for my applet/apps.
[stuff deleted]
|
|
|
| Re: How do I reduce the size of Eclipse 3.2 memory footprint? [message #252015 is a reply to message #252012] |
Tue, 11 March 2008 19:55 |
| Eclipse User |
|
|
|
Originally posted by: kwarner.uneedspeed.net
I looked in my JDK installation -- I don't have JConsole. WTF???
What do I have to do to get it???
DemonDuck wrote:
> Thanks Michael,
>
> I needed a jump start for my memory. I get to doing things a certain way
> and forget all the other details ...
>
> Michael Pellaton wrote:
>
>> Hi
>>
>> Eclipse does not load all installed plug-ins (osgi bundles) during the
>> startup. Bundles are loaded when needed
>
> [stuff deleted]
>
> I forgot then remembered that the way to set memory params is in
> eclipse.bat
>
>> JVM parameters are the way to assign memory to Eclipse. All parameters
>> (Xmx, Xms, XX:PermGen, ...) work as expected.
>
>
> I've never used JConsole and now I must ask -- how do I do that in Eclipse?
>
> Again, the JConsole of the
>
>> JDK is a great tool for hunting memory issues as it offers graphical
>> monitoring of the different JVM memory areas and sizes and their usage.
>>
>
> Tell me about it :-(
>
>> I must admit depending on what features you plan to use and the size of
>> your projects, it will be tough finding good settings with 512MB of
>> physical RAM, especially as Windows already occupies quite a lot of it.
>>
>> HTH
>>
>> Michael
>>
>> DemonDuck wrote:
>>
>>> Environment: Win2k SP4; Java 1.5.0.9; 512meg memory;
>>> As you see, I have an old slow, tiny machine. Running Eclipse 3.2
>>> sometimes I run out of memory for my applet/apps.
>
> [stuff deleted]
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07015 seconds
Home