Dynamic CRM 2013 study notes (7) tracking, monitoring and performance optimization

This article describes how to track, monitor, and optimize CRM. Tracking is a very useful function in CRM. It can provide valuable information for our CRM to debug or solve errors and warnings; we can use the performance monitoring tool of window to understand the performance of CRM. Finally, we can adjust the performance of CRM and its database to make CRM optimal.

 

I. Tracking

There are two tracing methods. One is deployment level. This method tracks roles and services on all CRM servers. By default, log files are stored in c: \ crmddrop \ logs; the other is server-level tracing, which only tracks the server roles and services running on the current machine. By default, log files are stored in c: \ Program Files \ Microsoft Dynamics CRM \ trace.

If both tracing methods are activated on a server, only deployment-level tracing is run.

 

1. Deployment-level tracking

• Open powershell through run-> powershell
• Reference CRM command:Add-PSSnapin Microsoft.Crm.PowerShell
• First check the current tracing status: Get-crmsetting tracsettings
• Enable tracing:

  $Setting = Get-CrmSetting TraceSettings$Setting.Enabled = $True $Setting.CallStack=$True$Setting.Categories="*:Verbose"Set-CrmSetting $setting

• Disable tracing:

  $Setting = Get-CrmSetting TraceSettings$setting.Enabled = $FalseSet-CrmSetting $setting

 

2. Server-level tracking

• Open Registry
• Find HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ mscrm
• Create a New DWORD Value traceenabled. If you set the value to 0, it indicates disabled, and 1 indicates enabled.
• Create a New DWORD Value tracerefresh in the range of 0-99,
• Add a value of the string or multi-string type tracecategories in the format of category. Feature: tracelevel. For example, application. *. error will capture all errors in the application.

The following is a list of tracecategories. The default value is *: error.

• Create a New DWORD Value tracecallstack. 1 indicates that the call stack will include the tracing log. 0 indicates that the tracing log is not included. The default value is 0.
• Create a New DWORD Value tracefilesizelimit in the range of 1-100. This value specifies the maximum value of the trace file, which is 5 by default.

 

Ii. Monitoring

1. log on to the CRM server and start running-> Run-> perfmon. MSC to open Performance Monitor

2. Select monitoring tools> Performance Monitor.

3. Click the plus sign below

4. Add the following counters

5. Click OK.

 

 

Iii. Performance Optimization

• DB Optimization

1. Place the data files and log files on different physical hard disks, so that the data and log I/O activities can be performed simultaneously.

2. Considering the increase in data volume in 3-6 months, set the appropriate database file size

3. consider increasing the data volume in 3-6 months, and set the appropriate auto-increment size.

4. Increase the initialization and automatic increase of tempdb

5. Create indexes for extended and custom entities

6. set maximum degree of parallelism (maxdop) to 1

7. Added sqlcommandtimeout and aggregatequeryrecordlimit.

Use mscrm_config
Go
Update deploymentproperties set intcolumn = 9000 where
Columnname = 'sqlcommandtimeout'

 

Use mscrm_config
Go
Update deploymentproperties set intcolum= 100000 where Colum
Nname = 'aggregatequeryrecordlimit'

 

• System Optimization

1. deploy CRM on different servers based on roles and use network load balancing

2. Dynamic and Static content is compressed in IIS

3. Set maxconcurrentrequestspercpu to 5000

4. Set the IIS application pool to about 1 hour

5. Set the output cache in IIS to JS configuration.

6. Set the timeout value

Hkey_lcal_machine \ Software \ Microsoft \ mscrm

• Oledbtimeout 86400
• Extendedtimeout 1000000

 

 

Dynamic CRM 2013 learning notes (1) plugin input entity Parameter Parsing

Dynamic CRM 2013 study notes (2) Basic plug-in usage and debugging

Dynamic CRM 2013 learning notes (3) quick creation of entity entitycreater

Dynamic CRM 2013 learning notes (4) Document No. and plug-in batch registration tools

Dynamic CRM 2013 study notes (5) prohibit modification of approved documents

Dynamic CRM 2013 study notes (6) backup and recovery

Dynamic CRM 2013 study notes (7) tracking, monitoring and performance optimization