โ07-08-2021 06:05 AM
we currently have a pipe that queries salesforce via SOSL for search results. Using a normal *non ultra) pipeline task with a bearer token. When are using json to recieve and parse information then returning (non mapped) json to the requester.
This whole process takes 10 seconds which in production is an eternity.
Sample request:
{
โcontentโ:
{
โlanguageโ:โen_USโ,
โregionโ:โNorth_America__cโ,
โcustomer-typeโ:โCustomer__cโ,
โkeywordโ:โtheโ,
โrequiredFieldsโ:โtest1,test2โ
}
}
Sample result:
[
{
โTitleโ: โtest1โ,
โID__cโ: 84
},
{
โTitleโ: โtest2โ,
โID__cโ: 75
},
{
โTitleโ: โtest3โ,
โID__cโ: 132
}
]
The results are very small so is the packet being sent in. Its also worth noting the pipe has a router determining a URL parameter for path that has 9 options.
โ07-09-2021 03:58 PM
Hi Paul:
I would suggest logging a support ticket for this. These kind of issues often require some research. Being able to inspect pipeline execution and logs super helpful. 10 seconds does seem less responsive for this query, but again, not familiar with size of data, etc. Actually, the pipeline execution would help identify where most of the time was spent.
โ07-12-2021 11:10 AM
Can you break down how youโre measuring the 10 seconds?
Mind sharing a breakdown of the pipeline execution according to the Dashboard? If you donโt want to share publicly, you can reach out to support and they can share the results confidentially with us.
If you click on the pipeline status in the dashboard
youโll get a break down of the pipelineโs execution, which may give some hints at where the pipeline is spending time.
A general rule of thumb: