Why is there a discrepancy in total workflow time and can combining node code steps in a single step optimize speed?

1

This topic was automatically generated from Slack. You can find the original thread here.

Hi - trying to optimize the speed of my workflows and have a few questions. Would appreciate any insight.

  1. A workflow takes overall ~60-70s to complete but each individual step when added together amount to ~18s. Even when the workflow is warmed up. Why? I do have a number of disabled steps, is that impacting it at all?
  2. if I have a number of node code steps in a row, is there a material impact on speed combining those into one step versus keeping them separate? I imagine there might be some environment setup duplication
2

If you look at a specific execution that took a long time to complete, and trace the timestamps from the execution start and each of the steps Details section (or Logs), where do you see the delays?

3

When I look at every enabled step, they add up to ~18 seconds. Total time to complete the entire workflow is ~70. Is there something happening with disabled steps?

4

I gotcha, just trying to review which steps took more time

5

And if there were delays in between steps

6

If you trace the execution timestamps for each and every step

7

Guess I’m not following. If I look at the total workflow executed time, it shows as ~70s. When I go to every step detail and add those up, I get a total of ~18s. What’s driving the discrepancy? I do have 7 disabled steps I can’t click on so do not provide any execution time details

8

Can you share the workflow URL so I can take a look?

9

thanks

10

I would look at workflows from ~1pm est

11

Looking, thanks

12

The details tab for each step contains the timestamp for the execution for that step

image.png

13

So I’m looking at which steps took more time and where are the delays

14

Yeah trying to reconcile with this

image.png

15

Workflow started execution at: 2:00:50
1st step: 2:01:06
2nd step: 2:01:06
3rd step: 2:01:07
4th step: 2:01:08
End execution: 2:02:01

16

Looks like most delays occurred before the first step and after the last step

17

One other weird thing that happens with this workflow (that might add to the puzzle) - When I’m testing out some particular node steps, it sometime starts what looks like a test of other node steps (just indicated by that other step showing the spinner icons). Not sure if there’s some weird environment spillover between steps including the disabled steps

18

I had never seen that with my previous workflows

19

Hmm I’ve never seen any indications before whether paused steps took execution time or not

20

Something that helps reduce the total execution time a lot is raising the memory to 512 MB