Microsoft Dynamics AX (Archived)

Performance tuning AX

(0) Share

Report

Posted on by Mohana Yadav

61,005 Super User 2025 Season 2

Hi All,

Need your help to check whether there is any scope to improve the performance in below scenario.

Client is using AX2012.

Is integrated with 3rd party solution

3rd party solution will be sending 16 csv files with total size of 50MB and 5,00,000 invoice records to import into General Journal.

It is taking more that 24hrs.

How can we reduce the time of import?

Please let me know what else can we do to improve the performance and what is the approx. effort to estimate?

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Mea_ 60,284 on at

Like (0)

Report

Hi Mohana Yadav,

Obvious solution here is multi-threading using batch framework. I can see 3 different tasks to do in parallel:

1) Upload files in parallel.

2) Create journals in parallel.

3) Post journal in parallel.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

Hi Mohana,

You need to monitor the servers on CPU, memory and disk usage (latencies). In addition you can look for long running queries or missing indexes in SQL server management studio. Also indexes might be fragmented.

You can also use the AX Trace parser and/or DynamicsPerf to capture some data for invetigations what is exactly happening and where the performance can be improved.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

If you have batch AX AOS servers with the recommended 8 CPU cores, you could distribute the load on 2 batch servers by using separate batch groups for each file or group of files (with 16 threads if HyperThreading is enabled). 1 file would be processed in 1 main batch job that would read the files into a staging table. Then the batch job will start spawning off additional runtime batch tasks, which pick up each line from the staging table and create it in the proper journal and stamping with the recid of the batch task int he staging that which one is currently being processed. You could also add a status to your staging table to track if there were any errors during the import, like missing information or invalid dimension combinations etc.

Actually the Data Import Export Framework is capable to handle large data imports, you might want to take a look at that as well.

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

If you are looking for performance improvements without significant code change you should follow Andre's advice.

However, if you want to redesign solution it worth to look at DMF as well. Is uses SSIS and batches out of the box so it should not be too long to build new entity, here is a nice explanation of this feature timsaxblog.wordpress.com/.../recurring-batch-job-import-in-ax-2012-r3

Was this reply helpful? Yes No
Suggested answer

Mohana Yadav 61,005 Super User 2025 Season 2 on at

Like (0)

Report

Thank you all for your suggestions.

We are ready to redesign also.

What will be the approx. time to redesign using above suggestions?

so you guys are sure that importing time can be reduced from 24hrs to approx time?

We are on AX2012 and not 2012R3. the blog post still works in AX2012 also?

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

Hi Mohana Yadav,

It's probably impossible to give you any estimates without doing actual analysis of your code and system setup, same with performance increase.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

If you are new to DIXF, then it could take a 2-4 weeks for a good AX developer to understand the framework, deploy it in Dev/Test and in Production, take a look at the existing entities to see how much of your CSV import is covered (and if you have customizations in the financials module especially tables/fields/views/maps, ledger posting classes or financial dimensions), then decide if it will be an existing entity or a new, custom made DIXF logic. Someone experienced could do the whole thing in possibly a week.

Since DIXF consists of both binary and AX application components, installation itself does involve an outage on Production, to start with. You could possibly do the framework installation and code deployment in one go once your import code is ready and tested in the pre-production environments.

AX 2012 RTM and R3 versions of DIXF are slightly different, you can read about that in the documentation on LCS/MSDN.

Was this reply helpful? Yes No