Idle time in the Process Model for simple expression rule

Certified Lead Developer

Hi Guys,

Our client checking the node timings for each step in the process in that time we noticed the simple expression rule took around 1 to 1.5 seconds, however the same rule checked in direct expression rule it took only 1ms. Can any one facing this type of issue? Any solution for this. Please find the below examples,

Example:

Obj: Sharing simple example below which i done for testing perspective.

Expression rule logic: elapsedtime(now(),now()+52) => took 1ms

Call the rule in process model(without activity chaining) => took around 500 ms.

Thanks,

Pradeep Sridharan

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    This is the expected behavior. Appian is made to scale to millions of in-flight processes. BTW, Appian does not spend that much time on trying to evaluate your code. This is just the way Appian executes process nodes. Does this lead to a specific problem for you?

  • 0
    Certified Lead Developer
    in reply to Stefan Helzle

    We are checking the performance for end to end business to improve more in the design. In that we are seeing this issue.I mentioned to customer,  Appian having some idle time and its expected behaviour. Here I am confirming again is there any solution.

    Thanks,

    Pradeep Sridharan

  • 0
    Certified Lead Developer
    in reply to Pradeep Sridharan

    Before talking about solutions, does this lead to any problem? What do you mean with "performance" and what would you want to improve?

  • 0
    Certified Lead Developer
    in reply to Stefan Helzle

    In our process, we have two Webapi and checking the timeline for the API, please find the below scenarios,

    First Webapi Logic - Client system calling Appian API to save the value , after save Appian share the request id as response and calling async multiple integrations(6 services) as parallel.

    The response for all the services (which are calling as async) as approved or rejection.

    Second Webapi Logic - Once First Webapi response as request id, immediately client system calling second Webapi and waiting for the service response as approved or rejection, If any service still running api response as pending. 

    Hence, as per the business logic currently we are checking how much time it takes start from first api to second api (until get approve or reject).

    All the services are returns min 1 to 2 seconds in the postman. but each process of service in Appian took some idle time along with prepare request or response logic. In that, we are checking the logic of request or response rule took in expression rule very minimal time compare with process level. 

    Thanks,

    Pradeep Sridharan

  • 0
    Certified Lead Developer
    in reply to Pradeep Sridharan

    I understand. Thanks for the explanation. I still want to know whether this is a problem, or just not what has been expected.

    So, you can dramatically speed up process execution by enabling process chaining. BUT, this is not recommended as it can lead to excessive system load and slow downs for other processes and/or applications. Use this only when the normal process execution speed becomes a real problem.

Reply
  • 0
    Certified Lead Developer
    in reply to Pradeep Sridharan

    I understand. Thanks for the explanation. I still want to know whether this is a problem, or just not what has been expected.

    So, you can dramatically speed up process execution by enabling process chaining. BUT, this is not recommended as it can lead to excessive system load and slow downs for other processes and/or applications. Use this only when the normal process execution speed becomes a real problem.

Children