AX2012 Technical Track - Infrastructure, Davy Vliegen

Microsoft Dynamics AX 2012 Infrastructure

November 24th, 2011

Davy VliegenProactive Dynamics EngineerMicrosoft EMEA Customer Support & [email protected]

2

Objectives

Give a quick overview of the Microsoft Dynamics AX 2012 system architectureDiscuss ‘Day in the life’ benchmark studyProvide the first sizing guidelinesShow what is still expect to come in terms of sizing help

Agenda

Overview of Microsoft Dynamics AX 2012 system architecture‘Day in the life’ benchmark studyMicrosoft Dynamics AX 2012 sizing guidance

GeneralFor each AX component

Future help on sizingResourcesQ & A

Microsoft Dynamics AX 2012 system architecture

‘Day in the life’ benchmark study

Done in August and published in October 2011

CustomerSource: https://mbs.microsoft.com/customersource/documentation/whitepapers/ax2012_benchmarkpapersPartnerSource: https://mbs.microsoft.com/partnersource/deployment/documentation/whitepapers/ax2012_benchmarkpapers

Variety of functional scenariosDifferent client and integration technologiesGoal: Providing a view of ERP workload performance on Microsoft Dynamics AX 2012Simulation of 5135 concurrent usersSustained rate of more than 1 million lines per hour

‘Day in the life’ benchmark study Rich client simulation

Core account receivable scenarios: from order entry through invoicingQuotation management (Sales quotations)Item ArrivalsTransfer ordersPayment processing

Enterprise PortalCreate timesheetsPurchase requisitions

WorkflowPurchase requisitions converted into Purchase orders

Services and Application Integration Framework (AIF)Generate Sales Order lines

Batch processingCreate and post General ledger journal linesInvoice the Sales Orders received through Services and AIFPurchase orders posted to general ledger

‘Day in the life’ benchmark study

‘Day in the life’ benchmark study

Throughput measurements:

‘Day in the life’ benchmark study

Utilization summary:

‘Day in the life’ benchmark study SQL Server specification

4-processor 12 core (48 cores)2.2-GHz AMD Opteron processor256 GB of RAM64-bit version of Windows Server 2008, Enterprise Edition64-bit version of Microsoft SQL Server® 2008 R2 (Build 10.50.1797)

AOS servers specification10 AOS servers, 8–12 cores, 16 GB of RAM64-bit version of Microsoft Windows Server® 2008 R2 Enterprise Edition – Or– 64-bit version of Windows Server 2008 Enterprise Edition with SP2

Enterprise Portal server specification1 Internet Information Services (IIS) server, 8 cores, 16 GB of RAM64-bit version of Windows Server 2008 R2 Enterprise Edition with SP2

Visual Studio Ultimate client specification3 controllers, 14 agents2–8 cores, 4–8 GB of RAM64-bit version of Windows Server 2008 Enterprise Edition with SP264-bit version of Visual Studio 2010 Ultimate

‘Day in the life’ benchmark study

Database disk configurationHP logical volume SCSI disk driveDisk volumes are RAID 10

Data volume40 physical disks, 15,000 revolutions per minute (RPM)2.67-terabyte volume1.90-terabyte data file

Log volume 4 physical disks, 15,000 RPM273-GB volume46.7-GB transaction log file

TempDB data and log volume6 physical disks, 15,000 RPM410-GB volume48x2-GB data files20-GB transaction log file

‘Day in the life’ benchmark study

Comparison ‘Day in the life’ benchmark study Microsoft Dynamics AX 2009

‘Day in the life’ benchmark study

AOS Servers split by Microsoft Dynamics AX rich client users, Enterprise Portal users and batch processing

‘Day in the life’ benchmark study None of the servers were hyper-threaded1.5 – terabyte database with no page/row compressionIndex tuning has been doneCode performance tuning has been doneNumber sequence caching (non-continuous)Hotfix KB 2590260 – Item arrival line creation very slow through ineffective query – implementedDatabase in Simple Recovery modelMax degree of parallelism on 1SQL Server Max server memory on 258048 MB or 252 GBNo SQL Server trace flags were usedBatch job alerts have been turned offAccounts Receivable credit limit checks usedCache Limits for all AOS instances have been increased

Agenda update

Overview of Microsoft Dynamics AX 2012 system architecture‘Day in the life’ benchmark studyMicrosoft Dynamics AX 2012 sizing guidance

GeneralFor each AX component

Future help on sizing

16

Core Sizing Considerations and Influences

17

Guidance on Transactions Vs User Count

Size by Transaction Volume (Specifically Line Volume)Number of Concurrent Users is a required tenet but is secondary to transactions.Consider the Parameters/Data Composition under which transactions are being executedConsider Reporting Volumes and Report Types (Transactional/Trends/Detailed Listing etc)Define Multiple Peak Periods, if different

18

Guidance on Concurrency

Named Users ARE NOT Concurrent UsersConcurrent Users are always Subset of Named UsersPeak Workload defines Maximum Concurrency for SizingCRITERIA for Concurrent User:

Logged On ANDWorking Transactions/Inquiries at the time of Counting ANDNot an IDLE SESSION

19

Sizing guidance for each AX componentStorage

SQL ServerAX database (application data and model store)SharePoint databases (content and configuration)Reporting Services (SSRS)Analysis Services (SSAS)

Application Object Server (AOS)User activity (rich client, EP)Batch processingAIF processingWorkflow

Remote Desktop Session Host Server (RDSH Server) / Citrix ServerIIS server

Enterprise Portal / Role CentersEnterprise Search ServerHelp ServerWeb services (also AIF web services)

Integration componentsApplication Integration Framework (AIF)Office Add-insProject Server integrationMicrosoft CRM integration

20

Guidance on StorageSAN solution:

Choose one that fulfills all needs of businessLet vendor of SAN system decide on disk configuration

Keep in mind that:You get performance through having enough IO capacityIf you have bottleneck in this area it can be at the side of the discs having not enough capacity or from the controller who has too much workloadOn top of that; a memory bottleneck can lead to a disc bottleneckSizing for your Storage is based on performance optimization rather than data sizeSo it is always better to decrease the size of the individual disks then to decrease the number of disks

Sizing tips:Use Transaction Counts and indicators from Benchmarks/Internal testingAlways size for worst case scenario (peak hours, end of month...)Drill down to level of IO per seconds (IOPS)A 15K RPM disk should able to handle around 180-200 IOPSSAN vendor should know how to scale SAN based on IOPS figure

21

Guidance on SQL Server15K Lines Per Hour Per Core on Database Server for Microsoft Dynamics AX database (application data and model store)

This can vary a lot based on:Parameter Settings being usedLevel of CustomizationUsage of additional functionality like databaselog and alerts etc.

6 GB Memory for Each CoreUse the Benchmark report(s) for Comparative Sizing

Legal NoticeThe information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.  Information in this presentation, including URL and other Internet Web site references, is subject to change without notice. This presentation and its contents are provided in AS IS condition, and Microsoft does not guarantee the accuracy of any information presented. MICROSOFT MAKES NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE INFORMATION CONTAINED IN THIS PRESENTATION. © 2011 Microsoft Corporation. All rights reserved.

22

Guidance on SQL Server (II) SharePoint databases (content and configuration):

As long the data is stored in Dynamics AX, the SharePoint databases can co exist at the same SQL server for Dynamics AX

Analysis Services (SSAS):Memory: 4 - 8 GB per processor coreIf SSAS is on same box as SQL server instance running AX production database; they will eat each others memory, better to but SSAS on a separate server boxSSAS uses OLAP databases, or cubes, stored on the file system.Processing of OLAP databases is read and write-intensiveInfrastructure Planning and Design: http://www.microsoft.com/downloads/details.aspx?FamilyId=AD3921FB-8224-4681-9064-075FDF042B0C&displaylang=en

Reporting Services (SSRS):Memory: 2 - 4 GB per processor corePlanning a Deployment Topology: http://technet.microsoft.com/en-us/library/ms157293.aspx Planning for Scalability and Performance with Reporting Services: http://msdn.microsoft.com/en-us/library/cc966418.aspx#XSLTsection129121120120 Infrastructure Planning and Design: http://www.microsoft.com/downloads/details.aspx?FamilyId=AD3921FB-8224-4681-9064-075FDF042B0C&displaylang=en

23

Guidance on Application Object Server (AOS) Split by AOS servers for Microsoft Dynamics AX rich client

users, Enterprise Portal users and batch/AIF/Workflow processingAOS servers for rich client users

Multiple Instances can run on same box when using Processor AffinityUse Transaction Counts and indicators from Benchmarks/Internal testing5K Lines Per Hour Per Core2 GB Memory for Each CoreUser Concurrency is a good Marker. Based on Transaction Complexity, between 25 Users Per Core to 150 Users Per Core (average of 60)

Legal NoticeThe information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.  Information in this presentation, including URL and other Internet Web site references, is subject to change without notice. This presentation and its contents are provided in AS IS condition, and Microsoft does not guarantee the accuracy of any information presented. MICROSOFT MAKES NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE INFORMATION CONTAINED IN THIS PRESENTATION. © 2011 Microsoft Corporation. All rights reserved.

24

Guidance on Application Object Server (II) AOS servers for Enterprise Portal (EP) users

Multiple Instances can run on same box when using Processor AffinityUse Transaction Counts and indicators from Benchmarks/Internal testing7K Lines Per Hour Per Core2 GB Memory for Each CoreUser Concurrency is a good Marker. Based on Transaction Complexity, between 25 Users Per Core to 150 Users Per Core (average of 120)

Legal NoticeThe information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.  Information in this presentation, including URL and other Internet Web site references, is subject to change without notice. This presentation and its contents are provided in AS IS condition, and Microsoft does not guarantee the accuracy of any information presented. MICROSOFT MAKES NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE INFORMATION CONTAINED IN THIS PRESENTATION. © 2011 Microsoft Corporation. All rights reserved.

25

Guidance on Application Object Server (III) AOS servers for batch/AIF/Workflow processing

Multiple Instances can run on same box when using Processor AffinityUse Transaction Counts and indicators from Benchmarks/Internal testing15K Lines Per Hour Per Core2 GB Memory for Each CoreBatch Threads: the default value is 8. To determine the correct value:

AOS Size – Number of Cores/Processors. A Single Processor can do between 1 and 4 threads (depending on workload)Type of work being executed. If it is database centric, then the # of threads is a parameter of the database server IO/CPU/Memory in that order. If they are not database centric but X++ heavy, Line 1 appliesDegrees of Parallelism across your workload. If you have parallel capable processes, then you can go with higher threads (otherwise, there is no point).

Legal NoticeThe information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.  Information in this presentation, including URL and other Internet Web site references, is subject to change without notice. This presentation and its contents are provided in AS IS condition, and Microsoft does not guarantee the accuracy of any information presented. MICROSOFT MAKES NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE INFORMATION CONTAINED IN THIS PRESENTATION. © 2011 Microsoft Corporation. All rights reserved.

26

Guidance on RDSH Server / Citrix Server Remote Desktop Session Host (RDSH) Server: New name in

Win2008R2Client memory considerations drive sizingWhat else are you running on the server?

Office etc.

What controls are you running on the client?Browser controlsCustom controls

Base client sizing guidelines50 MB to 200 MB per client Instance. Usage determines peak memory footprint per client. Use client configuration settings to manage memory.Additional controls will have additional footprint

Latency guidanceRDSH Server / Citrix Server is NOT required when:

Bandwidth constraints do not exist User interactions on client require 6 or fewer round tripsLess than 100 milliseconds peak latency (expected delay of approximately 600 ms)

RDSH Server / Citrix Server IS required when:The above conditions cannot be metWAN environment that uses legacy X++ reporting

Future help on sizingMicrosoft Dynamics AX 2012 Hardware sizing best practices guide planned to be releasedMore benchmark studies in pipeline:

AX 2012 Terminal Services benchmarkAX 2012 EP technology benchmarkAX 2012 Services AIF benchmarkAX 2012 Hyper-V benchmarkAX 2012 Retail benchmark

Hardware sizing tool still to be plannedBusiness partners:

Contact your Services Account ManagerContact Advisory Services: [email protected]

Customers:Ask your business partnerContact your Technical Account Manager (Premier contract)Contact PFE Dynamics Enablement Assistance [email protected]

ResourcesMicrosoft Dynamics AX 2012 System Requirements guide

http://www.microsoft.com/download/en/confirmation.aspx?id=11094

Microsoft Dynamics AX 2012 “Day in the Life” BenchmarkCustomerSource: https://mbs.microsoft.com/customersource/documentation/whitepapers/ax2012_benchmarkpapersPartnerSource: https://mbs.microsoft.com/partnersource/deployment/documentation/whitepapers/ax2012_benchmarkpapers

Microsoft Dynamics SureStep 2012https://mbs.microsoft.com/customersource/downloads/servicepacks/MSDSureStepdownloads.htm

Microsoft Dynamics InformationSourcehttp://informationsource.dynamics.com/rfpservicesonline/

Microsoft Dynamics AX Performance Team Bloghttp://blogs.msdn.com/b/axperf/

Microsoft Dynamics AX Sustained Engineering Bloghttp://blogs.technet.com/b/dynamicsaxse/

Microsoft Dynamics AX Technical Support Bloghttp://blogs.msdn.com/b/emeadaxsupport/

Thanks to

Diamond Sponsors

Gold Sponsors

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after

the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Q & A

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after

the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.