Hi there,
For a HTTP response that is about 70MB, it takes about 8-10 minutes for the element to retrieve the response and due to that, all the other actions and sessions are blocked for that duration as well. It is not a timer or trigger issue as I have tried replacing the call with another URL that has a lightweight response and that completely removed the blockage.
I have checked that the SLport.exe retrieves the response at a rate of around 100-300kb using Resource Monitor and that roughly coincides with the time taken by the element.
What would be the available options I have to mitigate this issue?
Any help is appreciated! Thank you!
Hi Jackson,
The big response can indicate that you are polling a bit too much data at once. I would advise checking the API documentation if there is no option to split up the request. If this is not the case maybe the vendor can be contacted to check the most efficient way to retrieve the data.
More context:
The XML response is critical to many tables in the driver so it would seem, to the user, that the sets do not work since the change won’t be reflected until 10min later. I guess solving the blockage of other actions is one thing but getting the response promptly is a bigger challenge.