Exposed Process/SOAP performance

[rj.latherow]

Hello - we have a few processes that are exposed as API (SOAP, we are on the latest 6.10 version).  These processes are very simple and either record a request as a queue item or return a status- in both cases the pages take seconds to run on their own.

When run as an API request, they are SLOOOOOW- sometimes just under a minute, and the fastest I have been able to see is around 20 seconds on the very rare occasion.  Average response time is ~42 seconds, which is not acceptable for what we are doing.

Is there any way to increase the throughput/response time on the gateway?  The machine is dedicated to this simple task, so it isn't a resource issue.  I am on the cusp of scrapping the solution and finding a path forward that isn't limited by BP's performance.

[Denis__Dennehy]

I think you probably have to go down a network latency testing rabbit hole first, a SOAP api call to add a new queue item should be be almost instantaneous.

Have you tested the exact same functionality running local to you in a test sandbox - hosting a test BPServer instance to see how fast that is comparted to your live environment.  What is the spec of the BPServer machine,  maybe compare it to online advice about the specification required for a fast soap service server.   Also ask your IT department to grab some network sniffer tools to test issues in network speed between your robots and the BPServer.

If the SOAP calls are going slow I would also expect other things to be going slow in your live environment when network calls are made.  How long does it take the live robots to load a BP Process before running it etc..