Limit the number of asynchronous jobs picked up for each organization
Update Rollup 3 for Microsoft Dynamics CRM Server 2011 introduces a new deployment-wide setting that limits the number of asynchronous jobs that may be picked up for each organization. This setting may help reduce asynchronous operation backlog when multiple organizations are present. Without limiting the maximum number of jobs picked up, if a single organization in the deployment submits a large number of asynchronous jobs, such as 3,000 jobs, the Asynchronous Service may attend to those jobs first instead of attending to the fewer number of jobs submitted by other organizations.
The following Windows PowerShell command sets the maximum number of items that can be queued to 100 for each organization in the deployment.
|You must apply Update Rollup 3 for Microsoft Dynamics CRM Server 2011 or a later version update rollup on all Microsoft Dynamics CRM server roles before you run this Windows PowerShell command.|
To configure the number of asynchronous jobs picked up for each organization
add-pssnapin Microsoft.Crm.Powershell $itemSetting = new-object 'System.Collections.Generic.KeyValuePair[String,Object]'("AsyncSelectMaxItems",100) $configEntity = New-Object "Microsoft.Xrm.Sdk.Deployment.ConfigurationEntity" $configEntity.LogicalName="Deployment" $configEntity.Attributes = New-Object "Microsoft.Xrm.Sdk.Deployment.AttributeCollection" $configEntity.Attributes.Add($itemSetting) Set-CrmAdvancedSetting -Entity $configEntity
Send comments about this article to Microsoft.
© 2013 Microsoft Corporation. All rights reserved.