Boosting the Performance of your Eclipse IDE
4 likes1,613 views
This document provides tips to boost the performance of the Eclipse IDE. It discusses where performance issues commonly occur like startup time, build time, and UI responsiveness. It then provides solutions in several areas like hardware configuration, Java settings, workspace resources, plug-in development, and preferences to optimize Eclipse performance. Specific tips include using a RAM disk, latest JDK, server JVM settings, disabling indexing, splitting projects, reducing compiler warnings, and profiling tasks.
Boosting the Performance of your Eclipse IDE
- 1. Boosting the Performance of your Eclipse IDE Karsten Thoms EclipseCon Europe, Ludwigsburg, 2015-11-05
- 3. Where performance issues are annoying Startup Build UI Responsiveness
- 7. Wow! That was too easy!
- 9. Hardware
- 10. Hidden costs of waiting
- 11. Configure Anti-Virus JRE/JDK Eclipse Installation Folder ~/.p2 Workspace Folder Project Folders Output Locations http://www.stockvault.net/photo/180403/cyber-security-concept-with-umbrella-on-data-screen
- 12. Disable Indexing OS indexes every changed file Consumes CPU & IO Usually senseless for build output and workspace metadata Can only be disabled easily for directories, not by file types Programmatically: Spotlight: Flag File .metadata_never_index Windows: attrib.exe /s –i *.*
- 13. RAM Disk
- 15. RAM Disk What to store? Read-only Data JRE Bundle Pool Output folders Use Symbolic Links Store / Restore state to/from persistent storage
- 17. Eclipse Installation Don’t store Eclipse / Workspace on Network Share Use a current Eclipse distribution Don’t install every feature any team member might use Different feature set for different tasks? Expensive: Mylyn, Subversion Use Oomph setups or Eclipse Profiles
- 18. eclipse.ini Java Settings Use the latest JRE Use Server VM Use enough Heap Increase Young Generation Space Disable Class Validation Turn on Compiler Optimizations Activate Parallel GC -vm /Library/Java/JavaVirtualMachines/ jdk1.8.0_66.jdk/Contents/Home/bin -server -Xms512m -Xmx2g -Xmn512m -Xverify:none -XX:+AggressiveOpts -XX:+UseParallelGC
- 19. Workspace Resources Close unused projects Close unused views Close unused perspectives
- 22. Split Projects
- 23. Resource Filters
- 24. Compiler Warnings Reduce compiler warnings If you ignore them anyway, filter them Ignore optional warnings on selected source folders (e.g. generator output)
- 25. Plug-in Development Target Platform Mirror/Aggregate Public p2 Repositories b3 Aggregator, Buckminster, p2 Tools Deploy on Local Network / Repository Manager Launch Config for Eclipse Application Required bundles only Disable API Tooling during development Enable on demand, in CI, before milestones
- 26. Cleanup Metadata Clean JDT index <WS>.metadata.pluginsorg.eclipse.jdt.core Resource History <WS>.metadata.plugins org.eclipse.core.resources.history PDE caches / Bundle Pool <WS>.metadata.pluginsorg.eclipse.pde.core or even fresh workspace http://www.stockvault.net/photo/133998/recycling-grunge-sign
- 27. Preferences
- 33. Maven
- 34. Disable Check for Updates
- 38. References “7 Tips to Speed Up Eclipse” http://www.nicolasbize.com/blog/7-tips-to-speed-up-eclipse/ „15 Useful Tips - Speed Up Eclipse To An Ultra Fast IDE" http://www.fromdev.com/2013/05/Speed-Up-Eclipse.html „How to quickly make eclipse faster“ http://howtodoinjava.com/2014/04/05/how-to-quickly-make-eclipse-faster/ “Benchmarking G1 and other Java 7 Garbage Collectors” http://blog.mgm-tp.com/2013/12/benchmarking-g1-and-other-java-7-garbage-collectors/ Alex Blewitt: “Eclipse start optimisation” http://alblue.bandlem.com/2015/09/eclipse-optimisation-part-2.html Lars Vogel: “Eclipse Activator startup sins – Tracing the startup time” http://blog.vogella.com/2015/09/16/eclipse-activator-startup-sins-tracing-the-startup-time/