Strange Local Variable Performance

Certified Associate Developer

I have been working on improving the performance of my interface, and I came across some performance results that I don't understand. I have a local variable (local!initialData) that calls an expression rule. I have a second local variable (local!dataCapture) that is just a copy of local!initialData. Looking in the performance tab of the interface, both of these local variables take the exact same amount of time to evaluate (+/- 1ms). However, I would expect local!initialData to take longer than local!dataCapture since local!dataCapture is just copying the data from local!initialData, not running the expression rule.

Can anyone explain this to me? Is this to be expected, or am I doing something wrong to cause this to happen?

I have attached an image of the performance numbers for these two local variables and have included the definitions of both below.

Thanks in advance!

local!initialData: a!forEach(
    local!orderLineData,
    rule!SSTH_initialData(
      orderLineData: local!orderLineData,
      index: fv!index,
      desiredOutput: "dataCapture"
    )
),
local!dataCapture: local!initialData,

  Discussion posts and replies are publicly visible

  • 0
    Appian Employee
    in reply to Jack Ferguson

    Just curious, what's the overall performance of the interface? I don't know if you have other stuff in the interface or not, but if you isolate it to just these two variables is the interface taking 2 seconds to load or 1?

  • 0
    Certified Associate Developer
    in reply to Peter Lewis

      This interface is pretty large, but I was able to comment out everything but these two variables and a couple other local variables they depend on. When I tested the interface the total evaluation time is 1,457ms and each of the local variables is 1,325ms. I have attached a screenshot of the performance results below.

    I guess that would be a good indication that Mike is correct in saying what he said earlier (quoted below), and local!dataCapture is not actually taking as long to evaluate as the performance evaluation is indicating.

    the downstream one is showing a similar number only because it's waiting on the prior dependent, i.e. the total time isn't even necessarily the combination of the two numbers