>> I found that this version still suffers from the the memory consumption issue.
Has this been logged with support?
I've been running SQLDev on Windows 7 with default JVM settings for about 2 weeks. I've even sleeped the machine at least 5 or 6x in that time period.
According to Windows, the sqldev EXE process has about 800MB of memory allocated for it - whether the JVM is actively using that memory for SQLDev is another issue, but as you know jvisual VM can answer that question. Anyways, I've seen no issues with the responsiveness of the application. It's even been running ORDS that entire time too, not exactly a best practice...but I am pretty mean to SQLDev so I can surface issues hopefully before a customer would ever see them.
Anyways, we're not looking to 'fix' anything, b/c no issue has been identified. I'm not saying your issue isn't real, I'm just saying it's not been observed as an actual problem internally, or by a customer to My Oracle Support so we can troubleshoot and fix it if necessary.
What version of Java are you running? Have you investigated tuning any of the JVM parameters?
1 person found this helpful
If your goal is to get the OS to reclaim memory allocated to the JVM (have the JVM release allocated memory), you might want to look into using the Garbage-First Garbage Collector. That is the only one of the various available collectors in which I have seen that occur... https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/
For some other JVM tuning goals, review this blog... https://blogs.oracle.com/ardaeralp/tune-your-jdeveloper-12c-1213
1 person found this helpful
Thank you for the response.
I have not logged a ticket with Oracle Support but have tried multiple JVM parameter changes in the past per older discussions but none had ever resolved my issue. Only a bounce of the application would do that. Since it is a freely available tool I did not believe I should be logging a support ticket but I will certainly do that and provide whatever details Oracle Support wishes to see.
I am running on Windows 7 on a VMWare machine with 6GB of RAM.
Here are the contents of the "About" extract.
Oracle SQL Developer 126.96.36.199.089
IDE Version: 188.8.131.52.42.170225.0201
Product ID: oracle.sqldeveloper
Product Version: 184.108.40.206.089.1709
Oracle IDE 220.127.116.11.089.1709
Java(TM) Platform 1.8.0_121
Name Identifier Version Status Registration Time Initialization Time Total Time
==== ========== ======= ====== ================= =================== ==========
It's included with your database license, so it's part of the database.
>>I am running on Windows 7 on a VMWare machine
What if you run it on the Win7 host? Running it in a VM won't speed anything up.
I can run it on a Windows 7 machine instead of on VMWare but I do not have admin rights on that system to configure it the way I need a development machine to be configured to work with other tools. So I am stuck with the VMWare machine.
I'm not sure what that means, there's no configuration per se in SQLDev that requires windows admin rights - but it would be useful to know if we remove the virtualization bits if it runs any better for you.
Are you running SQLDev with a 64 bit JDK in the vm?
I mean that I would need the full environment setup with all the tools I need, not just SQL Developer and without admin rights I am unable to setup that full development environment.
SQL Developer is running as sqldeveloper64W.exe and using the JDK that came with it that has the following attributes per the SQL Developer properties panel:
java.version 1.8.0_121 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.121-b13
Still don't know what you mean, b/c SQLDev can be setup and run w/o admin rights, AND it can connect to anything on your VM. But regardless, take another look at Gary's advice on the jvm parameters. That's your best bet..unless you want to give more memory to your jvm and your image.
Or, just close SQLDev at the end of each day.
Since SQL Developer does not do everything I use other tools like Ruby/RSpec, Cygwin(with many tools), Subversion/Tortoise, etc. that I need installed on the development system. Without these other tools in addition to SQL Developer I would need to constantly switch between the system where I have admin rights and they are all installed and the system where I do not have admin rights but SQL Developer is installed. That would not be very efficient.
Thank you for the advice. I'll be sure to let others know to continue to just bounce it.
there's a SVN client built in, just in case you didn't know
Thank you. I had used the built in Subversion functionality years ago but then the server and the version in SQL Developer got out of sync and had to stop using the version in SQL Developer. I keep meaning to setup it up again and start using it again.