topic Building a Job With xms and xmx Parameters in Talend Studio

Building a Job With xms and xmx Parameters

VRadhakrishnan1651487711 — Fri, 15 Nov 2024 22:21:24 GMT

Hello Friends

Good Day

I have few questions regarding the xms and xmx parameters.

I have a Job which is a parent job which has xms as 512 and xms as 1024 and the parent job calls a a job(child job) which as xms as 512 and xms as 1024. When i run it, will take the RAM memory around 2GB? or less than 1024. (Consider im running an complex job with millions of records to process)
If i remove the xms and xmx job from both Parent and Child Job. On what basis does the job will be run.

Kindly help me to clarify these doubts. Thanks in Advance

Regards,Vinoth

Re: Building a Job With xms and xmx Parameters

Anonymous — Thu, 17 Nov 2022 04:53:32 GMT

Hello,

During your job execution, does an OutOfMemory Java exception occur? Is it OK with you to allocate more memory to your job execution?

We will appreciate it a lot if you could give us more description and information about your current situation and the getting issue.

Best regards

Sabrina

Re: Building a Job With xms and xmx Parameters

Anonymous — Tue, 22 Nov 2022 09:26:26 GMT

Hello,

If your tRunJob uses a separate process to run the child job then you'll have 2 java processes.

Xms mean that Java should allocate that much memory, so in your case depending on your settings it can be 512 to 1024 megabytes minimum.

Xmx mean that Java can allocate UP TO this amount of memory. In your case this could mean anywhere between 1 and 2 gigabytes of memory.

Hint if you're not storing a lot of data inside (no huge tMap lookups, excel files, etc) then most talend jobs could run 100 megabytes of memory.

If you enable Java flight recorder you can review the memory usage of your job. Or you can do it live via VisualVM: https://community.talend.com/s/article/Using-VisualVM-to-record-Java-Issues?language=en_US

This gives you the exact numbers, so no need to guesstimate.

Cheers,

Balázs