Performance with Triggered task
As part of our project requirement, we are using Triggered task and observed that performance is not as expected.
So, can someone help to understand whether the trigger task has some latency in gen...
Forum Discussion
Triggering a task through a cloud url and ground url are now substantially different. The flow of a cloud triggered task will go through the SnapLogic Control Plane, where as the On premise URL has been optimized to try and avoid making any requests to the Control Plane when possible. Another difference is that any data passed in or out will be proxied through the control plane with a cloud url. Where as with the on-premise URL, your HTTP client connects directly with the Plex. So the on premise URL should have a substantially lower latency in most cases, especially if executing on a ground plex that’s co-located with the client.
The Cloud URL is convenient to use when the client might not be on the same network as the Plex as it allows connectivity, but if you can use the on premise URL, then that’s generally a better way to go.
@tlikarish Cloud url has a limit (Total API limit (per day):10000, is there any limit for ground url?
Nope – since a Groundplex runs on a customer’s infrastructure it is not bounded by any limitations.
