1 person found this helpful
I'd like to know if there is a way to identify if RTSM leaves a thread hanging in the background after window exits?
I think that is unlikely, but perhaps someone else will have more insight into that. Instead, I would suspect Java memory limits and garbage collection overhead, so...
For general performance tuning of the IDE itself, it is best to refer to tuning information for the JDeveloper IDE upon which SQL Developer is based: https://blogs.oracle.com/ArdaEralp/entry/performance_tuning_jdeveloper_12c
1. Whenever there is a reference to jdev.conf substitute sqldeveloper.conf (in 4.2 installation's...\sqldeveloper\sqldeveloper\bin)
2. Whenever there is a reference to ide.conf substitute product.conf (in C:\Users\<your_user>AppData\Roaming\sqldeveloper\4.2.0)
In my experience, adding these settings to the default sqldeveloper.conf and bumping up the memory limits a bit in product.conf from the defaults of 128M min / 800M max does seem to make the UI a bit snappier. I usually go with 256M / 2048M. Probably a combination of more aggressive garbage collection and a higher memory limit will help to avoid the slowdown you experience. I do note a warning message when starting up SQL Developer from a Cmd window...
warning: Using incremental CMS is deprecated and will likely be removed in a future release
but recommendations like those in the blog above evolve over time, taking advantage of whatever latest and greatest switches become available.
Thank you Gary Let me test this out.