SQL Developer Memory Footprint

Question

We're looking at replacing around 200 TOAD licenses with SQL Developer. The only technical concern is the memory footprint, as in many cases it would be run from a terminal server with dozens of people logging on. A VM Size of 150MB seems to be not unusual for SQL Developer, and that all adds up of course.
Are there any recommendations for reducing the memory footprint, or at least not letting it get much higher than 150? Features that can be turned off by default, versions of JDK, etc?

Answer 1

Hi,
The memory consume is quite worrying.
However change the code into VB / Delphi will lose its availability as Java's write once run anywhere. :-)
You won't be able to use this tool on Solaris, Linux, and Mac without changing the code and compiler. Thus would be less acceptable.
I wonder if limiting SQL Dev's initial class load would give impact on memory consume.
And why it seems that Java's garbage collector didn't do any collecting since the memory gets higher and higher time by time.
Or maybe the code doesn't allow the object's become collectable?
I ever get memory reach up to 500MB after doing a canceled Export Wizard for USER.
But..... memory would never come down.
Regards,
Buntoro