Skip to main content

NAV 2013 R2 - Sizing Guidelines For Microsoft Dynamics NAV 2013 R2.

Hi All,

Microsoft have released one of the most awaited document for Microsoft Dynamics NAV 2013 R2.

"Sizing Guidelines For Microsoft Dynamics NAV 2013 R2 for On-premises Single Tenant Deployment"

The Sizing Guidelines can be downloaded From PartnerSource -

Below are some Bytes from the Document "Microsoft Words"-

The test results demonstrate that with the loads described it is possible to run 500 concurrent users, each executing up to 90 transactions per hour on a single Microsoft Dynamics NAV Server instance with 16 GB of RAM and a Quad Core Processor at 2.45 GHz.

Based on the test results, our recommendations for sizing Microsoft Dynamics NAV Server for single tenant on- premises usage are:

> Up to 150 users per CPU core on each Microsoft Dynamics NAV Server instance.
> Minimum 5 MB memory per active user on each Microsoft Dynamics NAV Server instance.

Simulated Concurrent User Load -

During the test run, we increase the user load by 20 users every 10 minutes. Half the users run transactional scenarios and half run consulting scenarios. Thus at a load of 200 users the test agents are executing 9000 transactional scenarios and 5400 consulting scenarios per hour. The combined workloads correspond to the following actual test scenario and task rates per second.

IMPORTANT - The sizing guideline does not cover the requirements for the Microsoft Dynamics NAV Windows clients, as the goal is to simulate an environment where each client is a separate machine.

When deploying Microsoft Dynamics NAV Windows clients using terminal services, you must consider the resources consumed by each client process

Sizing Conclusions for Single-Tenant On-Premises Deployments -

Resources consumed by Microsoft Dynamics NAV Server instances The following recommendations are based on the resources metrics collected from the test machines at the start of the test run and at the maximum load of 500 users.

Memory Requirements 

At the peak load of 500 concurrent users the memory consumed by the Dynamics NAV Server process was approximately 3.3GB.

Each user session that connects to a Microsoft Dynamics NAV Server was calculated to need approximately 5 MB of RAM per user, this takes into account the operating system and initial server memory requirements.

A rule of thumb for sizing is that each processor core is capable of handling up to 150 users at the loads described.

So let's Download the Document and Start Exploring what in the Document for us.

I hope this will put us in a better position in front of customer while discussing the Hardware Requirment.

There will be Some Things i would Still Like to See on this Document - 

  1. What is Suggested Physical / Logical Disk for Placement of Database Files?
  2. How much free disk space should be there in the Disk where Database Files are Placed?
  3. No. of Temp Databases Files?
  4. Size of Temp Databases?
  5. Suggested LAN / WAN Configuration?

I Hope these will be part of the Document in Future. So let's be happy that we had something for NAV which we can present to Customer.

Thanks Microsoft Team for the Document.

Stay Tuned For More.

Saurav Dhyani


Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.