May 4, 2011 at 1:37 pm #316549
If you are having performance issues in MyEclipse 2015, please click here for more information that might help.
1) myeclipse.ini settings
If you are using a 64-bit installation of MyEclipse, you may want to increase the memory settings in myeclipse.ini; 64-bit software really does consume more memory and our tests have shown that the increase can be as high as 30 to 40%. You may need more memory even on a 32-bit install, if you have a large workspace.
The myeclipse.ini file can be found in the same folder as your MyEclipse executable. Open it in any text editor and change the values based on the size of your workspace. For instance, the following settings may be preferable to the defaults.
-vmargs -Xmx768m -XX:MaxPermSize=384m
MyEclipse 9.1 and later
Some background information:
In MyEclipse 8.6.1 we had custom JS solution that was highly efficient in terms of memory consumed. Unfortunately, this solution had to be withdrawn due to several other issues surrounding compatibility with third party plugins and we have moved back to an integrated JSDT solution. We have brought several of our custom JS enhancements to JSDT, but the memory issues remain unresolved and far from trivial to fix.
3) MyEclipse Configuration Center
Depending on your actions, the MyEclipse Configuration Center could consume a significant amount of memory. Though most users will not leave the configuration center open when closing the workspace, if you do so, it will reopen when you next start MyEclipse. You do not need to wait for the configuration center to open each time MyEclipse starts and can close it before it opens by pressing Ctrl + F8 or simply clicking the “Close” link.
I apologize for any inconvenience caused; our focus this year is on performance and efficiency so you should be seeing improvements constantly being made in this area over the next few releases