Skip to main content Skip to complementary content

Performance preferences (Talend > Performance)

You can set performance preferences according to your use of Talend Studio. To do so, proceed as follows:

Procedure

  1. From the menu bar, click Window > Preferences to open the Preferences dialog box.
  2. Expand the Talend node and click Performance to display the relevant view.
    Information noteNote: You can improve Talend Studio performance when you deactivate automatic refresh.
  3. Optional: Select the Deactivate auto detect/update after a modification in the repository check box to deactivate the automatic detection and update of the repository.
  4. Optional: Select the Check the property fields when generating code check box to activate the audit of the property fields of the component. When one property filed is not correctly filled in, the component is surrounded by red on the design workspace.
    Information noteNote: You can optimize performance if you disable property fields verification of components, for example if you clear the Check the property fields when generating code check box.
  5. Optional: Select the Generate code when opening the job check box to generate code when you open a Job.
  6. Optional: Select the Check only the last version when updating jobs or joblets check box to only check the latest version when you update a Job or a Joblet.
  7. Optional: Select the Propagate contexts added in repository context groups check box to allow propagating contexts newly added in repository context groups to Jobs.
    With this option enabled, each time you open a Job that uses a repository context group, you will see a dialog box asking you whether you want to perform a context propagation if any context has been added in the context group but not synchronized to the Job yet.

    This option is disabled by default.

  8. Optional: Select the Propagate add/delete variable changes in repository contexts check box to allow propagating variable changes in the Repository Contexts.
  9. Optional: Select the Activate the timeout for database connection check box to establish database connection time out.
  10. Optional: Specify a timeout value for the database connection in the Database connection timeout (seconds) field.
  11. Optional: Select the Add all user routines to job dependencies, when creating a new job check box to add all user routines to Job dependencies upon the creation of new Jobs.
  12. Optional:
    When working in a Git managed project, select the Automatic refresh of locks check box to allow Talend Studio to automatically retrieve the lock status of all items contained in the project upon each action made in Talend Studio. If you find communications with the Talend Administration Center slow or if the project contains a big number of locked items, you can clear this check box to gain performance of Talend Studio.
  13. Optional: Specify a timeout value in the Default connection timeout (seconds) field to define how long Talend Studio retries connecting to a server, for example Talend Management Console, Talend Remote Engine, Talend Administration Center, Talend JobServer, and Git, in case of a connectivity issue.
    The default value is 5 seconds. You can enter 0 to disable connection timeout and allow infinite retries.
  14. Optional: Specify a timeout value in the Default read timeout (seconds) field to define how long Talend Studio should wait for a response from a server, for example Talend Management Console, Talend Remote Engine, Talend Administration Center, Talend JobServer, and Git, before throwing a timeout exception.
    A smaller value helps improve Talend Studio performance, while a larger value prevents frequent connection timeout exceptions. The default value is 60 seconds, and 0 means no read timeout.

    The timeout for artifact repository connection is also specified in this field.

  15. Optional: In the Code Format timeout (seconds) field, specify the number of seconds in which you want Talend Studio to stop formatting the source code upon code generation, for example when you switch from the Designer view to the Code view or when you build a Job or Route. The value must be an integer greater than 0. Setting a small timeout value helps prevent performance issues at the price of lower readability of the source code, especially for a large, complex Job or Route.
  16. Optional: In the HBase/MapR-DB scan limit (for retrieving schema) field, specify the number of columns to be displayed for all the HBase/MapR-DB connection metadata.

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!

Leave your feedback here