Time required from issue to execution of AutomateC command

[sumire]

Hello,

On 2 servers of equivalent specifications, what is the possible cause if there is a difference of more than twice the time between issuing the process execution instruction command(AutomateC.exe /run...) and actually starting the process?

------------------------------
Mitsuko
Asia/Tokyo
------------------------------

[ewilson]

Hello @sumire,

I have a few questions:

• Are both servers on the same subnet?
• What are you using the call the AutomateC.exe? Is it a homegrown application, another Blue Prism process, or something else?
• When you call AutomateC are you invoking the same Blue Prism process in both cases?
• How are you measuring the time-to-start?
• Do you have available licenses?

Cheers,​

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

[sumire]

Hello @ewilson,

Thank you for your support.

• Are both servers on the same subnet?

No. Two servers are in two places that are completely unrelated.

• What are you using the call the AutomateC.exe? Is it a homegrown application, another Blue Prism process, or something else?

Another Blue Prism Process. I created both the process of calling and the process of being called.

• When you call AutomateC are you invoking the same Blue Prism process in both cases?

Yes. I exported and imported same processes to both environment.

• How are you measuring the time-to-start?

Process Log and Control Room

• Do you have available licenses?

Yes
​

------------------------------
Mitsuko
Asia/Tokyo
------------------------------

[ewilson]

Hello @sumire,

Apologies for the delayed response. The first thing that pops out at me is that the runtime resources are on different network segments which could call into question network latency. Ideally, I would conduct the test on two DW's that are on the same subnet and see if you encounter the same delay in startup.

Cheers,
​

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

[sumire]

Hello @ewilson ,

Thank you for your kind support.
I tested various combinations ( network , number of RRs , BP version , ...) and I think that number of RRs in the resource pool impacts performance.
How many RRs are recommended in 1 resource pool ?
​For concurrency, is there an alternative way to resource pool?

------------------------------
Mitsuko
Asia/Tokyo
------------------------------

[ewilson · Accepted solution]

Hello @sumire,

See this KB article regarding resource pools:

https://portal.blueprism.com/customer-support/support-center#/path/Installation-Platform/Configuration/Resource-Pools/1741351672/What-is-the-recommended-maximum-number-of-resources-in-a-Resource-Pool....​

The general recommendation is to limit resource pools to no more than 10 runtime resources (that includes the pool controller RR).

Are you trying to use Login Agent on these resources?

Cheers,


------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------