Batch Parallelism in AX – Part - IV

re: Batch Parallelism in AX – Part - IV

Ganas1 — Sat, 24 Mar 2012 13:29:19 GMT

Yes. Overloading of batch framework tables is independent of the number of batch threads. The example you have given should not pose any problem. But assume you have 2 million Journal transactions and each journal has just 2 lines means you have 1M journals. If you create 1M batch task to handle this load, irrespective of whether you have 32 batch threads or 64 batch threads you may see some performance impact.

re: Batch Parallelism in AX – Part - IV

Joe — Fri, 23 Mar 2012 21:52:09 GMT

If I understand what you mean by overloading the batch table, wouldn't that be independent of number of batch threads?

For example, let's say 1 million GL journal transactions. If each journal had on average 250 lines, then there would be 4000 batch tasks if 1 task was created to create 1 journal.

We have the ability to go to up to 64 threads on 32 cores.

re: Batch Parallelism in AX – Part - IV

Ganas1 — Fri, 23 Mar 2012 20:33:20 GMT

How large is your 'very large' workload? Based on the nature of the workload, you can spend few extra minutes before creating the bundle to find the right size. Combining 2 of the techniques is also an option. The number of task that can be executed in parallel, directly depends on the number of batch threads available on your batch servers first.

re: Batch Parallelism in AX – Part - IV

Joe — Fri, 23 Mar 2012 17:43:38 GMT

If the workload was both very large and uneven, what would the best approach be? I assume bundling with some kind of algorithm to split up the workload evenly. If we were able to do that, is there a max number of batch tasks that should be allowed per batch in order to not stress the batch framework? Is that number 100? 500? 5000? I suppose the number of batch tasks should also be dependent on number of cores on the DB server.