Improving Studio performance

Guidewire Studio uses a separate Java process to do its builds. To set the upper limit for the heap allocation of this process, set Build process heap size in the Settings dialog.

If your project compilation takes an excessively long time, or if you encounter an OutOfMemoryError, then the heap size may be too low. Try setting the heap size to a larger number. The heap size setting is a maximum value, not a dedicated allocation. Therefore, you could set it to the memory size of the computer, or even higher. If the machine has virtual memory available, a very high setting may result in swapping rather than an OutOfMemoryError. Ensure that your computer has enough memory to allow the compilation to run, while still running Studio, the operating system, and whatever other applications are necessary. Debugging while the application is running also consumes some of the available memory.

If you increase the heap size and there is still insufficient memory available for the compile process, then your computer is likely either overloaded or under-provisioned. One way to investigate this is to use a computer with more memory and resources. Set a high value for the heap size limit, run a full rebuild of the application configuration, and monitor the heap usage of the Java process that is doing the compile. For optimum compile time, set the heap limit above the value used by the compilation Java process. Note that a full rebuild requires more memory than an incremental compile.

As you continue to develop your configuration, you may need to increase the memory allocation.

See also

• Set the amount of memory for project builds in Guidewire Studio

Some computer systems run processes that scan every new or changed file, such as virus scanners and file indexers. In a Guidewire Studio development environment with frequent product builds, file scanning may reduce compilation performance. If you experience slow compilation times, disable any active file scanning processes.