Setting Memory Usage Configuration

By default, Aptana Studio allocates 128M to start (the -Xms128M parameter), and uses a maximum of 384MB (the -Xmx384M parameter), of Java heap memory, which is usually enough for most development tasks. However, depending on the JRE that you are running and if you are working with additional plugins and have many files open, you may need to increase your amount of memory. You may also find it helpful to increase the size of the permanent generation memory, which defaults to 256MB (the -XX:MaxPermSize=256m parameter).

In some situations, such as when you have many projects in your workspace or when a project under source control has many files, you may get better performance by increasing the maximum heap memory (the -Xmx384M parameter). However, setting the memory allocation larger than the available physical memory on your machine can cause issues with Java which will severely degrade your computer's performance and should be avoided.

Memory usage configuration changes are made in the AptanaStudio.ini file. Studio must be restarted for any changes to this file to take effect.

Certain parameters in the AptanaStudio.ini file are platform-dependent; For example, only OS X needs the XstartOnFirstThread parameter.

AptanaStudio.ini Across Platforms

Windows

-startup plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731 -vmargs -Xmx384M -Xms128M -XX:MaxPermSize=256m -Djava.awt.headless=true

OS X

-vmargs -Xms128m -Xmx384m -XX:MaxPermSize=256m -Xdock:icon=../Resources/aptana.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts

Linux

-startup plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar --launcher.library plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.101.R34x_v20080731 -vmargs -Xmx384M -Xms128M -XX:MaxPermSize=256m -Djava.awt.headless=true