Skip to main content Skip to complementary content

Showing JVM resource usage during Job or Route execution

About this task

The Memory Run vertical tab of the Run view of your Talend Studio allows you to monitor real-time JVM resource usage during Job or Route execution, including memory consumption and host CPU usage, so that you can take appropriate actions when the resource usage is too high and results in low performance of your Talend Studio, such as increasing the memory allocated to the JVM, stopping unnecessary Jobs or Routes, and so on.

To monitor JVM resource usage at Job or Route execution, do the following:


  1. Open your Job or Route.
    In the Run view, click the Memory Run tab.
  2. Click Run to run the Job or Route.
    You can click Run on the Memory Run tab to monitor the JVM resource usage by your Job or Route at any time even after you launch your Job or Route from the Basic Run tab.
    The Studio console displays curve graphs showing the JVM heap usage and CPU usage respectively during the Job or Route execution. Warning messages are shown in red on the Job execution information area when the relevant thresholds are reached.
  3. To view the information about resources used at a certain point of time during the Job or Route execution, move the mouse onto that point of time on the relevant graph. Depending on the graph on which you move your mouse pointer, you can see the information about allocated heap size, the 90% heap threshold, and the 70% heap threshold, or the CPU usage, at the point of time.
  4. To run the Garbage Collector at a particular interval, select the With Garbage Collector pace set to check box and select an interval in seconds. The Garbage Collector automatically runs at the specified interval.
    To run the Garbage Collector once immediately, click the Trigger GC button.
  5. To export the log information into a text file, click the Export button and select a file to save the log.
  6. To stop the Job, click the Kill button.

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 – let us know how we can improve!