Difference between revisions of "Platform UI/Juno Performance Investigation"
|Line 2:||Line 2:|
= Resolution =
= Resolution =
Several major performance defects have been addressed in
Several major performance defects have been addressed in Juno SR2 (4.2.2). Community members have confirmed that these fixes substantially address the performance problems with editor and view opening, closing, and switching. These fixes widely available in http://download.eclipse.org/eclipse//4.2Juno the release stream.
= Symptoms =
= Symptoms =
Revision as of 10:43, 14 May 2013
Many users have reported performance problems when using the Juno (June 2012) release. This page contains a summary of the problems found and how they were addressed.
Several major performance defects have been addressed in Juno SR2 (4.2.2). Community members have confirmed that these fixes substantially address the performance problems with editor and view opening, closing, and switching. These fixes are widely available in Juno Service Release 2 (February 2013). All defects are also resolved in the Kepler (June 2013) release stream.
- Symptoms are slow UI operations such as open and closing views/editors/perspectives
- Often the degradation only happens after prolonged usage, or when certain plugins are installed
- There are mixed reports of changing JVM version, vendor, or command line arguments improving the situation, but with no definite pattern
- Often but not always the slowness occurs with JEE or Android editors
- Similar symptoms are seen by users of various team providers
- Reverting platform version to Indigo with all other plugins the same, usually resolves the problem
The problems seem to fall into two general categories:
- Small but noticeable degradation in UI performance between 3.7 and 4.2 platform code base. For example in a fresh new workspace, opening an editor taking 100ms rather than 50ms. These problems are known and slow/steady progress is being made on improving it. In general these problems are due to having a completely new code base for the platform user interface. The 3.x platform had many years to optimize the critical code paths, and these optimizations will take time to make on the 4.x stream over the coming releases.
- Extreme degradation of performance, such as 3-4 seconds to open/close editors. These problems typically only occur after prolonged usage, and in conjunction with certain plugins. These were not reproducible using the plain Eclipse SDK, but manifest themselves in certain Eclipse packages and with certain user workflows. These problems were narrowed down to leaks or excessive events in the platform code, in conjunction with expensive listener computations in contributed plugins, combining to manifest the problem.
The main focus is on making performance fixes in the Juno stream. As the basis of the Eclipse Long Term Support program, the Juno stream is very important to stabilize and improve. A small set of fixes were made for Juno Service Release 1. Further fixes will target Juno Service Release 2 (February 2013). Builds towards Juno SR2 occur every week - see the 4.2 Maintenance Build section on the download page. Changes that are considered too risky for the service stream will be made in the Kepler stream (June 2013 release).
Community help is needed to test the fixes and report further problems. Many of these issues were only reported after the Juno release came out, and those who can reproduce the problems have been providing great input since then. We strongly encourage adopting Juno SR2 maintenance builds and verifying fixes, reporting further problems, and assisting with profiling and tests to narrow down the problems.
Some progress is being made towards running automated performance tests for the first time at eclipse.org. Test builds are running today, but it will be awhile before we have tools ready to extract and analyze the results. Anyone willing to help with writing performance testing infrastructure please get involved in bug 374441.
We do understand there are commercial Eclipse adopters who are not yet ready to migrate to the 4.2 release, for either performance or other reasons. On the other hand, the Eclipse Platform and releng team needs to focus its resources on one active stream, and we are confident that with community help we can advance 4.x to a point where it is acceptable for all. Contributions in the form of problem reports, test cases, and patches are essential for good progress to be made.
We are not considering any further 3.x releases after the 3.8.2 maintenance release scheduled for February 2013, though the code base and Eclipse.org build infrastructure will of course remain available for others who see a need to step up and maintain that stream.