Does anyone set target zones for task to job ratios? I'm wondering if this is a useful metric to track. On one side, if jobs > tasks, that means that many jobs are running, but performing no work. On the other hand, a high tasks/jobs ratio could indicate monolithic recipes, but are more likely to indicate high volume jobs processing individual records within a for each loop. Therefore, I'm thinking the higher the tasks/job the better, as long as you can address monolithic recipes somehow.
Curious to hear other folks thoughts!
Solved! Go to Solution.
In a review with Workato, they said they like to see jobs using less than 10 tasks per execution as a general rule of thumb. That's also assuming that these recipes are trigger-based and being executed frequently throughout the day. Obviously, if this is a batch job that just runs once per day, that guideline would change. I'd like to get the point where we have a sense for how many tasks we're consuming from each recipe or project, then as new integration requests come in we could estimate the task usage and make a decision based on the cost/benefit analysis and how many tasks we have remaining.
But... we're not even close to that. We've had some conversations with Workato about some tooling in that area.
After digging into this a bit, I've learned that funnily enough, we’ve been working on Platform Health KPI-type updates! While I don't have much more info than that at the moment, I'd love to hear other people's thoughts on the topic.
Please feel free to keep in touch your Workato rep for updates, and I'll be sure to update you here when I have more info for you. 🙂