#Eclipse ide performance software#

There are two supported ways of achieving this goal: In order to minimize start-up time, we want the JVM to bypass those heuristics and generate AOT code as much as possible. OpenJ9 has internal heuristics that decide when to generate AOT code. We also used a Class Data Sharing (CDS) adaptor that allows many of the Java classes loaded by the OSGi framework to be stored in the SCC. You can enable both of these features with the -Xshareclasses option, which is described in the OpenJ9 documentation.īecause the default size of the SCC is relatively small and Eclipse IDE is a rather large application, we configured a 100MB cache by specifying -Xscmx100m. Two features that were designed to help with start-up performance in the OpenJ9 JVM are the shared class cache (SCC) and dynamic Ahead-Of-Time (AOT) compilation. Therefore, using less memory in Eclipse can sometimes be important. Developers often have many applications and tools open at the same time, tools that might consume most of the RAM available on their desktop or laptop. For ease of measurement, we’ll focus on start-up time and ignore ‘smoothness’.

#Eclipse ide performance software#

Software developers want their graphical tools to start-up quickly and smoothly without any lag or stutter. The bake-off score sheet: performance metrics Because Windows is often used as a development platform and Eclipse is the most popular integrated development environment written in Java, we chose to evaluate the performance of OpenJ9 when launching an instance of the Eclipse IDE. So in this article we will look at how OpenJ9 fairs on Windows. To date, all of the experiments we’ve used to showcase the performance of the OpenJ9 JVM were carried out on Linux.