What are the optimal performance tuning settings to put in my sts.ini file to ensure STS runs well on windows?
My machine has 8GB of RAM and a 3.2 GHz Intel Xeon processor
First, you could start by watching your heap status
Window > Preferences > General > [-] Show Heap status
Remove unnecessary plugin loaded on the stratup
Window > preferences > General > Startup and Shutdown
Remove plugins you do not need (e.g. you could remove Mylyn Task UI, if you are not using Mylyn)
In STS.ini you could increase minimum Heap size, to minimize GC calls, and unlock experimental JVM options.
-XX:+UnlockExperimentalVMOptions
-Xms1024m
-Xmx1024m
Related
I'm using Eclipse Luna. As soon as I open this workspace java CPU usage goes to over 100% and doesn't go down. Doesn't happen with other workspaces. I tried several things, and they don't work:
Running ./eclipse -clean
Deleting the org.eclipse.core.resources folder in the .metadata/.plugins directory of the workspace and then reimporting all the projects into the workspace: this seemed to work yesterday, but today the workspace is freezing again.
I forgot to mention, it's not just CPU usage, the main problem is that the workspace is freezing and I can't do any action (can't edit code, can't open files, etc...). I think there's something corrupted with this workspace, because other workspaces work fine without increasing RAM availability. Tried the -Xmx thing, but it doesn't work anyway.
%CPU usage is fine showing more than 100% by using top command, doesn't mean that you are in trouble until its too high.
Actually Your eclipse need more memory to run.
you should run eclipse by passing Xmx args with more memory
./eclipse [normal arguments] -vmargs -Xmx1256M [more VM args]
I have a plugin project. When i debug this as an eclipse application, in the 2nd eclipse that opens, I want to open Project explorer window. As soon as I click on the button to do this, I get java.lang.OutOfMemoryError: PermGen space. I tried changing the PermGen space in the preference, but it did not help. Can any one please suggest a solution.
You should add the -XX:MaxPermSize=256m or 512m to the Window>Preferences>Java>Installed JREs preference page. Edit a JRE and add it to the Default VM arguments tab.
The eclipse native launcher uses the eclipse.ini to add extra permgen arguments to Oracle JVMs, but that information is not used during runtime launching.
What if you try to extend the memory of eclipse when it starts. To do that simply open the .ini file (inside your eclipse folder) and edit the lines that refer to permSize and memory size:
e.g.
-XX:MaxPermSize=500m
-Xms500m
-Xmx2000m
If you don't want to set the permgen size for EVERY launch, you can also add the Parameter to the Debug Configuration.
Run > Debug Configurations
Choose the "Eclpise Application"-Configuration on the right side and choose Arguments in the Tabs.
Add -XX:MaxPermSize=512m to the VM arguments:
-Dosgi.requiredJavaVersion=1.6 -Xms256m -Xmx4g -Dfile.encoding=UTF-8 -XX:MaxPermSize=512m
I often get this error "Operation linking viewer selection with current editor finished with errors" in Eclipse Galileo.
Once this error pops up no UI events is working in the IDE , i cant even able to close it also. Every time i have to go to task manager to stop the process , after this IDE works fine for some 5 min and again it display the same error as mentioned above.
i don't know what is happening , can you guys please help.
Just switch your Project Explorer to the Flat package presentation in Eclipse. It works :)
see details here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=530450#c7
Per the Eclipse manual:
PermGen is the permanent generation of objects in the VM (Class names, internalized strings, objects that will never get garbage-collected). An easy, if somewhat memory-hungry fix is to enlarge the maximum space for these objects by adding
-XX:MaxPermSize=128M
as an argument to the JVM when starting Eclipse. The recommended way to do this is via your eclipse.ini file.
If you are getting OutOfMemoryErrors while running Eclipse, the VM can be told to let the heap grow to a larger amount by passing the -vmargs command to the Eclipse launcher.
-vmargs
-Xms512m
-Xmx1024m
Alternatively, you can invoke the Eclipse executable with command-line arguments directly, as in
eclipse [normal arguments] -vmargs -XX:PermSize=512M -XX:MaxPermSize=1024M -Xmx1024M [more VM args]
Even with recent versions of Eclipse and Flat Package presentation, if you have a lot of large projects loaded this can still be a problem.
I've found however that if you break up your projects into working sets and minimise the amount of projects/tree nodes open by selecting a working set it can really speed up Eclipse and mitigate this problem.
I had this problem (Version: Photon Release (4.8.0)) and I fixed it by removing all breakpoints.
I am using Eclipse for development. However, it's is taking too much time to build.
It hangs when the percentage of build gets to 78. It shows "refreshing workspace" several times. That eats up lots of time.
How can I make Eclipse faster?
Increase the start-up memory as mentioned by thamaria
Disable spell check of eclipse
Disable the plugins which you never use it (myln etc)
Disable auto build.
This link might help you
http://pakkatechies.blogspot.com/2011/07/making-eclipse-ide-faster.html
There are many possibilities to tune Eclipse.
First, when Eclipse is hanging up you should start Eclipse with some arguments and give it more memory. Use: eclipse -vmargs -Xms256m -Xmx1024m or even more.
EDIT: "eclipse -vmargs -Xms256m -Xmx1024m" is the commandline command with which you can start Eclipse (well, depending on your OS). For that you either need to have eclipse in your environement path or you will have to use an absolute path to your eclipse executable file. Under Windows systems you may use for example "C:\Programme\eclipse\eclipse.exe -vmargs -Xms256m -Xmx1024m". You could f.e. create a short-cut with this command.
Second: If possible you can use several workspaces for your eclipse projects if they are not connected to each other. When using other projects than the ones located in your actual workspace switch the workspace to the one you desire. That way eclipse does not need to load all contents at startup and will therefor start much faster.
Third: You can disable the "build workspace" Option. Go to "project" --> and uncheck "build automatically".
In the project build properties, under behavior tag, check the 'Enable parallel build' box.
Eclipse Helios periodically starts running a job which displays "Computing additional info". During this time, Eclipse is very sluggish, bordering on unusable. What does this job do? Can I shut it off?
I just hope that someone in the JDT team comes to sense and gets rid of it, make it go faster, or at the very least change it to something meaningful.
Maybe this bug is related: Bug 293856 - [Browser] "Computing additional info" lag during content assist executions
Other than that:
Disable the virus scanner for Eclipse files (projects and the folder where Eclipse is installed). On demand scanning can cause severe performance problems with Java's lazy loading.
Disable all plugins that you don't need.
Give Eclipse more RAM (512MB or more)
Put 4GB of RAM into your computer. Costs nothing (
I discovered how you can fix this problem. Go to
Window > Preferences > General > Security > Secure Storage and click on "Clear Passwords"
It's computing/caching some information that will make some operations (like auto suggestion) faster.
I can only suggest several things:
if you installed Mylyn, try to disable the Task-Focused Content Assist
check the -Xms and -Xmx parameter in eclipse.ini
try to stop the auto build