nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

xCP autoactivties - performance

Imran_Yusubov

Hi Experts,

I have a workflow which has about 15 autoactivities.But most of the aoutoactivites doing really simple tasks, for example, one activity selects the performers deparyent name and index,one alters the case acl and grants permission to the receiver on the case, one creates a case log objects and so on.

if I did all of this operations in a single java class with a single autoactivity it would not take more than 5 second.But because the number of the auto activites when I start the workflow a task sent to the performers inbox about 1,5 -2 minutes.Is this is ok? Are there any way to increase the speed?

Is making 5 select queries with a single autoactivity creates the same load with making 1 selects with 5 auto activities?

Thanks in advance

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

DCTM_Guru

Yes, this is the observed behavior for Process Engine - it was optimize to support parallel processing and not necessarily sequential processing. This has been fixed with 6.7 SP1 with Stateless Process Engine:

• Improved performance since the stateless process executes completely in the method server in one thread and in one session.

• The Synchronous Invoke Process activity template supports input and output mapping. The standard Invoke Process template has input mapping only.

• If better performance is desired and the invoked subprocess contains only automatic activities, the stateless process engine is easily applied to an existing xCelerated Composition Platform (xCP) solution. Applying the stateless process engine involves replacing the Invoke Process activity with the Synchronous Invoke Process activity.

Invoking process instances using the Synchronous Invoke Process activity provides significant performance improvement. For example, during in-house testing the execution time of one workflow instance containing 20 activities was reduced from three seconds to 160 milliseconds.

Unfortunately, you will need to upgrade to 6.7 SP1 to take advantage of this OR like you said write your own custom server method.

All comments

DCTM_Guru

• Improved performance since the stateless process executes completely in the method server in one thread and in one session.

• The Synchronous Invoke Process activity template supports input and output mapping. The standard Invoke Process template has input mapping only.

Unfortunately, you will need to upgrade to 6.7 SP1 to take advantage of this OR like you said write your own custom server method.

Imran_Yusubov

Hi Johnny,

Thank you very much for the detailed response, "three seconds to 160 milliseconds" , this is a great improvement, happy to hear this.Writing custom method is not an option, because it requires a lot of time and also xCP stands for rescuing from coding.

20 activities and 3 minutes, are they in sequential or parallel order??? I mean I have 15 autoactivities which are doing really simple operations and it takes 1-1,5 minutes for the process to complete.

Actually 1-1,5 minutes is not very much time in real world but I am going to have a live presentation of the system to a customer, in presentation this time is quite a lot. Fortunately I have already upgraded the environment to 6.7sp1 but did not have time to check if the performance improved.

Johnny, I have one more question, what else I can do to make the sequential autoactivities run more faster.I have increased workflow agent threads but no change. Any ideas?

Thanks in advance

DCTM_Guru

I'm not a performance tuning expert, but the more threads you increased, the more time it may take for process engine to loop through all the threads. So each thread might would take longer to execute.

We eventually wrote custom server methods (as you described) - this was back in 6.5 SP2 days.

Imran_Yusubov

Ok, thank you very much, it was really helpful.

Miller-zzMST

Hi Imran,

Have you tried to play some with wf_sleep_interval and wf_agent_notify_newtask properties for Workflow Agent?

Imran_Yusubov

Hi Konstantin,

No, they have the default values I guess 5 sec.

Miller-zzMST

Could you try to decrease wf_sleep_interval or ensure wf_agent_notify_newtask is set to 'true'? I have not done serious performance reseaches, but it seems to me that the fisrt parameter could increase the perfomance a little. On the other side, I could not say that the enabled second parameter have noticeable increase in perfomance on my systems.

But this is just my subjective assessment, rather than the results of objective observations.

Imran_Yusubov

@Johnny,

You are right, in 6.7 sp1environment the same workflow runs in about 25-30 seconds at most.That is a great enhancement. Like it.