munge
asked on
Does a CRM 2011 workflow in a WAIT STATE use system resources, specifically the async service?
We have some workflows waiting on approvals. They show business process status = "Running". I read a blog that says wait conditions use resources via the async service (didn't say what: memory? CPU?).
My question is, does a wait condition in a CRM 2011 workflow use resources, and if so, what kind (memory, CPU, or both), and is it significant.
This question is coming up because our async service is spiking up to using over 36 gigs of memory during the day (at some point, the server then crashes).
My question is, does a wait condition in a CRM 2011 workflow use resources, and if so, what kind (memory, CPU, or both), and is it significant.
This question is coming up because our async service is spiking up to using over 36 gigs of memory during the day (at some point, the server then crashes).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree that using 36G memory is excessive. Do you have multiple CRM organisations in your deployment? The async service has to service each one.
Since you have on-premise you might want to have a look in the SQL database for the CRM organization and see how many rows you have in the asyncoperationbase table.
Since you have on-premise you might want to have a look in the SQL database for the CRM organization and see how many rows you have in the asyncoperationbase table.
ASKER
Actually, your last post just turned on the light bulb in my head. We actually have 3.5 MILLION waiting workflows! What I didn't think about, is that the async service is cycling through all those quite often...
Between that and a certain plugin we believe is in some kind of infinite loop, I think we're getting close...
Between that and a certain plugin we believe is in some kind of infinite loop, I think we're getting close...
ASKER
Also, would you happen to know how often the service cycles through those things?
No I don't. There's probably an article somewhere on the net about the inner workings of the async service but I don't recall seeing one.
ASKER
I guess technically you could say that using a database row is using resources, but to me "resources" means CPU and/or memory. And I would guess that the cycling through waiting workflows wouldn't take much CPU either. Certainly nothing that would push the async service up to using 36 gig of memory and crashing our system!
Thanks again.