I'm having a problem with System jobs in a database I have just migrated to V9.1 from 8.2.
In 8.2 I've never had an issue with the system performance in any aspect over 3 years but having moved to 9.1 I am having an issue where system jobs are sitting in the status of Waiting for Resources. The server is running at about 1% CPU and 84% Memory, so it is not contrained with physical resources.
Reading through this doc:
Dynamics Forum
| Microsoft Dynamics Community |
remove preview |
|
| Dynamics Forum |
| Recently our on-premise 7.0.0.3543 2015 CRM solution has had its async workflows freeze on an almost weekly basis, we checked the asynchoperationbase and there was only a maximum of 800 records there so it was unlikely to be the cause, however checking the logs revealed that queries (specifically set deadlock_priority low) were timing out and going over the threshold when this happened, it was suggested we increase the resources on the server hosting our asynch. |
| View this on Microsoft Dynamics Community > |
|
|
I have checked that the setting are as per 8.2 and they are identical.
The issue seems to be that I have a set of workflows that time out for 2 or 3 minutes for various reasons and that while these are sat at timeout, they are "blocking" other workflows from executing. There are system resources to process more system jobs so can anyone suggest what settings in the above doc link could be adjusted to allow more system jobs to execute at one time?
And any insight into anything that may have changed in the move to v9.1 would also be useful please. The only server difference is that we are now running SQL Server 2016 rather 2012, if that makes any difference?
------------------------------
Simon West
Nett Sales LLP
Aldbourne
------------------------------