Finance | Project Operations, Human Resources, ...

Multithreading

(0) Share

Report

Posted on by RahulD365

Hi Team

I have implemented multithreading in D365 Finance for one of the process, but looks like the process is running approx for more than 10 thousand records - it means my code is creating 1 Batch job with 10,000+ tasks in it.

Does this sound okay ? Because I see that batch job gets stuck and taking more than 2-3 hours to process the records.

Do you suggest to create multiple batch job header and add task (by dividing number of tasks as per the record count) ??

Please provide your valuable suggestions...

Thank you!

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi Rahul,

It depends on the tasks you perform in this batch thread. If you are updating records, ensure there will be no database locks; otherwise you will end up with an even larger execution time. You can indeed create multiple tasks. It would be an idea to make the bundle size or number of tasks configurable. Then you can try out multiple settings to see what would be optimal for your environment.

For your information the workflow processing batch job is creating tasks in bundles of 100 workflow instances. This is hard-coded. In one situation, we had performance issues with the workflow due to the number of legal entites, workflow configurations, complexity, etc. To solve these issues, I did propose to create workflow groups and made the bundle size configurable per workflow group. It solved the pains at this customer.

Was this reply helpful? Yes No
RahulD365 85 on at

Like (0)

Report

Thanks for the reply Andre!

When you say - "You can indeed create multiple tasks.", Does this mean - I need to create bundle size like 1000 tasks per batch(as a an example)

Suppose I have 10,000 records in my process - so you're suggesting to create 10,000/1000 = 10 batch headers and 1000 tasks in each batch header?? please confirm - because that's what I'm planning as well.

Do you have any sample scenario (X++) where they are looping bundle size, or create multiple batch headers and tasks underneath ....

Was this reply helpful? Yes No
Suggested answer

Sumit Loya 2,230 on at

Like (0)

Report

Hi Rahul,

Ideally you should never create more multi threaded tasks than maximum batch thread otherwise other threads would not execute simultaneously.

You are correct that you should limit number of tasks per batch header. Look at Project invoice posting in Batch in uses similar multi threaded concept for posting.

You can refer following blog for better understanding

Art Of Creation – Dynamics AX Blog » Batch multithreading

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,953 Most Valuable Professional on at

Like (0)

Report

If processing a single record doesn't take much time, the infrastructure to schedule and execute a task will take more time than the actual work, and you'll add this overhead ten thousand times. Therefore your process would consime much more resources and it might even compete later than if you just processed all records sequentially.

Using multiple batch headers wouldn't make any difference - you would still have ten thousand tasks.

What you should do is letting a single task process multiple records.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi Rahul.

You should not create 10 batch headers and 1000 tasks per header. Have a look at the workflow message processing batch job as an example. There is one batch job with one task. When the processing batch job is executed, it will create additional tasks for workflow messages in bundles of maximum 100. This is the example you can learn from. I suggested to make the bundle size or number of tasks configurable.

Was this reply helpful? Yes No