D365FO Performance. Periodic import of one million ledger journal lines

January 20, 2021

Sometimes you may come accross the following question related to D365FO performance: "Our customer has X transactions per day, can D365FO handle this?". The problem is that currently, Microsoft doesn't publish any D365FO performance tests and the current answer is: "You need to test it with your specific setup". In this post, I try to provide some steps to run a D365FO performance test. It will be for a standard Demo database, so it can be executed without big efforts.

Test description

This test is based on my previous post - How to implement file-based integration in Dynamics 365 FinOps using X++

It loaded 1000 files with 1000 lines each, so 1 million ledger journal lines were created.

To generate such test files I created a new form in the Tutorial integration module:

 PerfTestingMenu

 PerfTestingForm

It allows specifying a link to the Azure file share, a template for a file name, a number of files and a number of lines in each file.

When you press Create ledger journal files button it creates the specified number of files in the Incoming Azure file share folder.

FilesInAzureStorage

For a test data all possible values combinations for BusinessUnit, Department, CostCenter are used combined with 60* Main accounts for Credit, 50* Main accounts for Debit.

Even in the Demo database, there are more than 1 million different combinations, so all files will have different values for ledger dimensions.

FileStructure

Then I ran a Load messages task as a batch job and measured its execution time. It created and posted 1000 ledger journals(with 1000 lines each).

 ResultJournal

Test setup and preparation

To run this test I used a standard cloud DEV VM with 16HDD and the Demo database.

I did the following preparation:

  1. Installed DEVCommon and DEVTutorial models from https://github.com/TrudAX/XppTools repository.
  2. Created a new Azure file share and created a ledger message type linked to it

MessageTypeSetup

  1. Switched off DEV VM monitoring. It was creating a lot of load to a file system for my already not quite fast VM.
K:\Monitoring\MonitoringInstall-Uninstall.ps1
  1. Disabled Budget control. You probably will not use it for such large data loading.

BudgetControl

Budgeting - Setup - Budget control configuration

  1. Adjusted a Ledger account structure setup to allow any Business Unit, Department, Cost Center values for used Main accounts.

AccountStructureSetup

  1. Set Maximum batch threads to 60. This allowed me to fully utilize my VM.

BatchSetup

After that I generated 1000 files and ran the test.

Test results

I used a standard cloud DEV VM with 16HDD and the Demo database. I ran the test on 2 VM sizes:

  • Standard D8 v3 (8 vcpus, 32 GiB memory)
  • Standard D16s v3 (16 vcpus, 64 GiB memory)

For each VM size I decided to perform 2 tests:

I started with a fresh Demo database. Loaded and posted 1 million records, then generated the same set of files and loaded them again for a different date. So totally 2 million journal lines were created. The first test generated a new ledger dimension combination for every line, so it was like an initial data load. The second test used existing dimensions combinations, so it was like a periodic load.

The load operation consists of 2 batch jobs. The first reads files from Azure and puts them into D365FO tables. It is a single-threaded job and for both tests, the time was around 1.5 minute for 1000 files. Then the processing job(which is multithreaded) reads the file content from D365FO tables, generates and posts ledger journals.

I got the following times for loading and posting 1M ledger journal lines:

VM type First load time Second load time
Standard D8 v3 4h 40 min 3h 40 min
Standard D16s v3 3h 6 min 2h 29 min

TestResults

During both tests, CPU was used for 100%(about 25% for SQL Server and 75% for Batch service). Ledger journal classes contain a lot of caching and probably they are not optimized for different values for every single line as in this test.

CPUUtilization8

Of course, this test is quite simple, you should not use results from Tier-1 machines for Production planning, as Tier-2 VMs have a different architecture(SQL Azure instead of SQL Server), but I think the behaviour for Tier-2 will be the same: the more expensive service you use, the faster system will work.

I don't have access to Tier-2 VM now, also it is not clear what level of resources Microsoft gives you for Tier-5(Performance) and Production and how these resources operate comparing to local DEV boxes. If you have any information regarding this, please share it with us.

Summary

The cloud has some amazing capabilities. Even in this test by just one click(changing a VM size) I increased the load performance by almost 50%. But everything has its price. The current Dynamics 365 Licensing Guide has more than 50 pages, so the pricing structure is quite complex. And probably in the cloud world instead of asking "Can the system load 1M journal lines?" you should ask "What will be the cost of loading 1M lines in 2 hours?".

You can use the provided example for performance testing of File-based integration for D365FO. I uploaded files used for this post to the following folder.

I hope you find this information useful. As always, if you see any improvements, suggestions or have some questions about this work don't hesitate to contact me.


Tagged with:
Denis Trunin
Written by Denis Trunin

Get notifications about new posts on Twitter, RSS .