Skip to main content Skip to complementary content

Optimizing Talend Studio performance

If you experience slowness while working with Talend Studio, there are several ways to optimize its performance.

Hardware considerations

Make sure to check the Hardware requirements section of this guide. Keep in mind that those are the minimum requirements to be able to work with Talend products.

Qlik recommends you double the disk space required to avoid problems during high transactions.

For an optimized performance, Qlik also recommends to use a solid-state drive (SSD).

Adding Talend to the antivirus allowlist

Antivirus real-time scans can cause performance issues when a great number of files needs to be scanned.

One solution for Talend Studio slowness is to add Talend installation and workspace directories to your antivirus allowlist.

Look up your antivirus documentation for more information on how to add files and folders to its allowlist.

Editing the memory and JVM settings

To gain in performance at runtime and when launching Talend Studio you can edit the memory settings in the .ini file.

By default, the .ini file sets the following JVM parameters:

-vmargs
-Xms64m
-Xmx768m
-XX:MaxPermSize=512m
-Dfile.encoding=UTF-8                  
Information noteTip: The settings of the .ini configuration file will only impact the performance of Talend Studio, not the Job execution itself.
  1. Find and open the .ini file. The filename depends on your license and is either Talend-Studio-linux-gtk-x86_64.ini or Talend-Studio-gtk-aarch64.ini.
  2. Edit the memory attributes according to your system memory availability. For example:

    -vmargs -Xms512m -Xmx1536m -XX:MaxMetaspaceSize=512m

    Information noteTip: For big projects, you may need to increase Xmx to 4096m.

    For more information, see Frequently Asked Questions About the Java HotSpot VM on the Oracle website.

With 8 GB of memory available on 64-bit system, the optimal settings can be:
-vmargs
-Xms1024m
-Xmx4096m
-XX:MaxPermSize=512m
-Dfile.encoding=UTF-8

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!