Ultra pipeline response time
Hi everyone,
I’m testing the Ultra feature performance and I’m finding a results that are not so satisfying.
Using the new release 4.22 and even the old release 4.21 (including the patches): ...
Forum Discussion
We also saw this performance hit in the 4.21 upgrade but mostly using PATH parameters. First call you would see almost an 8 second hit and then any subsequent calls seemed normal. Change the path param value the 8 second hit came back. We reported this to support and it was acknowledge as a bug once we proved to them it was environmental. We just tested this with 4.22 after upgrading the plex environment in our dev environment. The initial problem does seem to be addressed but we are seeing more latency than before. Since it’s dev it difficult to truly tell if latency or normal. We typically have 200ms to 800ms response times depending on our pipeline. 800ms for just a JSON generator seems excessive. Have you reported that to Support?
Hi @murphy-brian,
Thank you for your reply. I’m still struggling with the above but the problem is also addressed to SnapLogic so waiting on some update.
When you look at the execution statistics in the pipeline runtime → Extra details, what are the runtimes shown there?
Are you using multiple instances of the Ultra pipeline?
Are you using a load balancer in front of your feedmaster ?
Is this running on a Groundplex or a Cloudplex?Hi @cstewart
Thank you for your interest on this topic. Below are the answers of your questions.
-
Extra details in the execution statistics
-
I’m using only one instance for this test pipeline but it is not something that is heavy used. I just occasionally triggering the pipeline from Postman to test the performances.
-
Yes, I can see in the Manager that the field ultra load balancer is populated with some address.
-
This is running on Cloudplex.
Please let me know if you need more details or if you find something that should be updated in order to improve the performance.
On your feedmaster node, what do the averages look like for the task? (Dashboard, FeedMaster Node->Additional Details)
I’d suggest you make a few requests, as with any process if it gets idle for any length of time, it gets swapped out. So the first invocation may be slow, but the subsequent requests should be fast(er). If that too is in the ms range, then the loadbalancer might need to checked by the SnapLogic Infrastructure Management team. (as it is a SnapLogic managed resource)
-
