Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

Announcing Optimizer for Eclipse – A Jetpack for Eclipse

Hello, Simon here – your friendly developer tools aficionado and developer advocate.

Today I am very excited to announce the release of Optimizer for Eclipse. Within the Java ecosystem, Eclipse is still the most widely used IDE. Yet, at the same time, it’s still a pain point for developer productivity. At some point, you have either thought, heard someone else say it or said it yourself: “Wow, my Eclipse is really slow today!”. It has recently been our goal to fix this, allowing Java developers to enjoy coding in Eclipse once again.


Optimizer for Eclipse is a totally free Eclipse plugin that detects and fixes common Eclipse configuration issues. These can add up over time and slow your Eclipse development environment down to a crawl. These issues include:

  • Insufficient memory allocation
  • Class verification overhead
  • Excessive indexes and history
  • Obsolete or slow JDK
  • Eclipse being out of date
  • Lengthy build and redeploy times

Optimizer for Eclipse evaluates your environment by performing checks on each of these issues. You can then choose which items you wish to fix and allow the plugin to automatically speed up your Eclipse environment. Oh and did we mention it’s free? Yeah, it is – totally free!

We caught up with Mike Milinkovich, Executive Director of the Eclipse Foundation:

“We are delighted to have ZeroTurnaround contribute to the Eclipse ecosystem, bringing its robust Java knowledge to the community and making it easier for our users to get the most out of their Eclipse IDE experience with Optimizer for Eclipse”

Have fun and enjoy coding in Eclipse, again!

Simon and the Optimizer for Eclipse team

Give it a go and see how much you can speed up your Eclipse environment!


  • jirkapinkas

    It would be nice if this worked on STS (Spring Tool Suite), right now it doesn’t work :-(

  • mirkoadari

    Stay tuned for the next release :) We’re working to get it supported.

  • Michael Keppler

    Seems my comment over at Simon’s blog was deleted. The current version 1.0.0 can lead to Eclipse not starting anymore. It seems to delete the lines

    when adding the XX:MaxPermSize line. At least on my Windows system eclipse cannot be started anymore afterwards. Only restoring the original 2 lines fixes this.

    And please add a link to an issue tracker at the product page.

  • Neeme Praks

    Removing that “–launcher.XXMaxPermSize” argument should not stop Eclipse from starting.

    However, this is not the proper place to troubleshoot this. Let’s take it to

    or send an email to

  • Neeme Praks

    We just released Optimizer for Eclipse 1.0.1 which adds support for Spring Tool Suite, among other improvements.

  • Neeme Praks

    We just released Optimizer for Eclipse 1.0.1 — this version is more careful when patching the INI file, trying not to overwrite existing settings if those are satisfactory (e.g. MaxPermSize of 256m is enough and should not be touched). There is also a link to support forums inside the plugin now.

    Thank you for your feedback!

  • jirkapinkas

    Wonderful! Thank you very much and keep up the good work!

  • Botulf

    Whats with the login? Cant have this in an isolated network!?

  • fgthjukipolm

    Install, see it need register, uninstall.
    Those dev should know better …