Very slow response times on API

[bennmasters]

We have noticed a significant slowdown in the response time on the simPRO API. In many instances we are waiting over 30 secs for a response to a simple query.

Is anyone experiencing the same problem? See attached for some screenshots demonstrating very slow response times. Our application is close to unusable at these speeds and so would really appreciate someone investigating this.

[robbertcha]

Hi,

We have tested the same request on your build for few times, and the response rime is around 6++ms - 7++ms, please check the screenshots on your private message box.

There is lot of reasons will slow down the response time, but it always caused by unstable internet connection, and please do let us know if the issue still happens on you, thank you.

[bennmasters]

Hi Robert,

Thanks for the response. We accept it is intermitent but it the slowdown is happening with such regularity that I'm sure if you tested a few more times you would find significant slowdowns.

I don't accept that its the internet connection here. This request is coming from one of our hosted application server on azure. We are not experiencing this with any of our other application integrations, just simPRO.

Do you log the requests that come into your API? Are you able to interogate those logs at the same time we made the api calls to identify whether or not its an issue at you end - I strongly suspect you will find it is?

Thanks,
Benn

[bennmasters]

See attached additional screenshot of call to api from postman showing a 14s response time on this occassion. there are times where it is <1s but other times where it is consistently much higher than that.

Also note in the bottom right of this screenshot the timing breakdowns. Transfer start is the same as "Waiting TTFB" on chrome dev tools which is defined as "The brower is waiting for the first byte of response. TTFB stands for "Time to First Byte". This timing includes 1 round trip of latency and the time the server took to prepare a response".

It is the simPRO server taking the time here not the tramission of data (which is only 386 bytes for this call).

Thanks,
Benn

[robbertcha]

Hi,

The delay could happens when too many requests are making at the same time, especially in a busy period. May I know how many attempts per sec your system making ?

[spolacsek]

Hi Robbert,

I am the developer that has integrated with the SimPro API for this build.

If it was a too many requests issue, shouldn't we be getting a 429? We get lengthy delays with a 200 or sometimes just a request timed out.

We would only have maybe 20 requests a minute... hundreds of requests an hour tops... only during business hours.

I can't imagine that it is because we are making too many requests.

Thanks,
Sean.

[robbertcha]

Hi,

We have now turned on API rate limiting (429 Error) on the API sandbox environments for partners only to test their integrations, so it is not ready yet for public.

We just found that there is more than hundred requests making in a short amount of time on your server log, and they are constantly, e.g.: 16:25 to 16:55 yesterday (14-Nov) the average amount is over 100, so do you mind to check on your code to see is there any unnecessarily requests are making.