Performance Impact of Long Running Timer in Workflows?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2014 07:19 AM
Recently we have noticed performance issue in our production instance. While reviewing recent changes we noticed that some of our workflows include long running timers and loops.
For example:
Activity: If a condition exists then send an email notification
Timer: Wait 3 Days
Loop back to Activity
Given that there are nearly 1000 active workflow contexts with this type of flow, could this be having a significant effect on overall performance?
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2014 09:04 AM
What kind of issues are you having? I don't think 1000 active wf contexts is very much and would have an affect on your instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2014 08:39 AM
Thanks for the feedback. We are having users make generic reports of "System Slowness". There are rarely details and the occurrence is occasional. We are currently reviewing recent update sets to determine if a recent change could be contributing to the problem. The workflow changes occurred recently, so we were interested in the potential impact of those type of changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2014 08:51 AM
Ok - from experience, performance issues - I do some basic checks and then engage with SN (HI Ticket). They find things that honestly, sometimes I don't think about or didn't realize could happen.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2014 08:56 AM
Those WF timers are normally just sitting on sys_trigger table, waiting for their time to happen. I wouldn't think they would have anything to do with it but you never know if the condition is maybe being constantly checked or something...
First of all, I would try to find out if it's client side or server side slowness, then you can look at transactions logs, client timing logs etc.
Active transactions can also help to see if there are any types of action that are particularly slow.
Slow SQL Log, could go on an on but his page is a good starter as well to start looking;
If it turns out to be client side, look at recent Client Scripts that have been added or modified.
If it's server side, look at Business Rules
Troubleshooting Performance - ServiceNow Wiki
