Garbage Collection: Sub Jobs and General Best practice

Seven Stars

Garbage Collection: Sub Jobs and General Best practice

Does the community suggest running java garbage collection after executing subjobs or is there a better way to deal with those errors when its not possible to add more hardware to the solution?

Moderator

Re: Garbage Collection: Sub Jobs and General Best practice

Hi,

Did you get "java.lang.OutOfMemoryError: GC overhead limit" issue?

The problem is that when failing with the “java.lang.OutOfMemoryError: GC overhead limit exceeded” error JVM is signalling that your application is spending too much time in garbage collection with little to show for it.

Usually, increasing the heap size with -Xmx parameter can give a quick fix for this kind of issue.

It is recommended that you check or profile the job design. Performance issue usually cause by the DB connection or the job design.

Hope this link will help:https://plumbr.eu/outofmemoryerror

Best regards

Sabrina

 

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

What’s New for Talend Spring ’19

Watch the recorded webinar!

Watch Now

Definitive Guide to Data Quality

Create systems and workflow to manage clean data ingestion and data transformation.

Download

Tutorial

Introduction to Talend Open Studio for Data Integration.

Watch

Downloads and Trials

Test drive Talend's enterprise products.

Downloads