Aces!!! You nailed it Gary...
I applied fixed noted in Re: Reduce SQLDeveloper memory footprint with JDK 1.7
For others, to summarize my changes.
comment the following two lines as shown below
Now SQL Developer runs at roughly 500 meg.
I guess the only thing I have left to ask others reviewing this would be if there is a way to get these memory values down without having much adverse impacts on SQL Developer based on newer JVM switches/functionalities.
The posts that drove these changes are old from a technologoical perspective :) 2010.
There is not much more I can contribute here -- perhaps others can. I will only say...
In terms of current Java HotSpot VM tuning options, see:
Also, if you are looking for sustained performance / quicker resumption after minimizing SQL Developer, don't forget this:
In terms of the G1GC algorithm, I would guess that the latest Java 7 update will be more finely tuned than the latest Java 6, but the recommendation is to stay with Java 6 until an upcoming SQL Developer release formally certifies on Java 7.
Thanks again Gary.
I'll give switch a shot as well.
Now, I only wish that the developers of OSD would provide a Preferences mechanism to apply these tweaks through the interface with a reboot option like some of the existing Preferences updates.
This might be a good extension option.
I wanted to add that I have been able to successfully get my OSD JVM Max Mem switch set down as far as 100M.
This works as long as I work with nicely tuned SQL and don't run huge selects returning unneeded data.
I have also found that dropping memory down this far has an impact on large XLSX exports.
However, if I need large exports, I try to use CSV to get around this, bump up my memory switch (would be nice to see extension for this) or use another tool.
I have found that the IDE disappears (can see it still in task manager) with a low memory setting if I do large dumps so I have to be carefull with that.
I'm even considering having two installations of OSD.
One Light (low mem) installation and One beast (high mem) of an installation where I can do large output dumps when occasionally needed.