Comments for Manuel Selva's Eclipse blog

Comment on JFace Bug 9262 by Russell Thamm

Russell Thamm — Fri, 23 Oct 2009 04:41:50 +0000

Thanks Manuel,

fortunately I realised pretty quickly about the bug (thanks to Javadoc).

I had no idea how to fix it until I read your post.

Comment on How do you handle OutOfMemoryError ?? by Angelo

Angelo — Fri, 25 Sep 2009 12:03:34 +0000

Hi Manuel, try increasing your heap size. You check the link below on how to do this on eclipse

http://javasprint.blogspot.com/2009/07/eclipse-shorcut-icon.html

Comment on Ant Recursive Delete by Alex

Alex — Tue, 15 Sep 2009 13:42:08 +0000

Thx!

Comment on Ant Recursive Delete by Max

Max — Mon, 07 Sep 2009 09:25:43 +0000

Thanks for saving me 30min

Comment on Draw2d Enhancements – Part 1 – Labels on Polylines by kentusha

kentusha — Fri, 28 Aug 2009 21:59:42 +0000

looks good, I would love to see the source good.

Comment on Integer- - by Ed Brannin

Ed Brannin — Tue, 25 Aug 2009 13:41:15 +0000

When I want to store an often-changing integer (often for a counter) in a Map or Collection, I sometimes use java.util.current.AtomicInteger (new in Java 5).

Comment on -Xms Question for long (French) week end by Daniel

Daniel — Mon, 13 Jul 2009 09:14:45 +0000

Setting -Xms tells Java how much memory the application gets right when starting up, regardless of whether it needs it or not.

It concerns other apps as any other memory that is in use: you don’t have it available for other apps. Depending on your resources this can mean swapping memory to HDD.

Another drawback (except of not having that memory available for other apps of course) of giving Java too much memory to handle is, that although a full garbage collection does not happen that often, it might take slightly longer, as there is more memory to handle.

Comment on -Xms Question for long (French) week end by Oleastre

Oleastre — Mon, 13 Jul 2009 08:16:54 +0000

From the java command manual it’s clear what those commands are used for.

-Xms is the initial (read the minimum if you want) heap size.
-Xmx is the maximum heap size.

From my experience, what is said in the doc to be the initial size is in fact like a threshold before the garbage collector starts running.

From the start of your JVM, a small amount of memory is allocated, and this one grows each time you need more memory. When -Xms value is reached, instead of directly allocating memory, the JVM tries to get back some by running the GC. At that time, if no memory is freed by the Gc, new memory is allocated, up to the -Xmx value.

So, it depends on the kind of application you work on, if it’s a desktop one, you will try to let some memory for other applications.

If it’s a server one, it’s probably ok to reserve the memory dedicated to your application.

From a performance point of view, this involves running the GC or not before allocating memory, it’s in fact the time your are ready to spend running GC.

Hope this help… and it does not contain too many errors

Comment on -Xms Question for long (French) week end by Markus Milleder

Markus Milleder — Mon, 13 Jul 2009 07:35:51 +0000

-Xms sets the heap allocated on VM start. Increasing it to the amount of memory your product typically needs will save you a few garbage collections and extra memory allocations during startup.

Comment on How do you handle OutOfMemoryError ?? by -Xms Question for long (French) week end « Manuel Selva’s Eclipse blog

Fri, 10 Jul 2009 14:55:43 +0000

[...] usage of our Eclipse’s based product. This work led me to ask my self How should I manage OutOfMemoryErrors and also bring me to -Xmx and to the mysterious (to my blinded eyes) -Xms [...]