RoundTrip Times

[gus]

I'm bit concerned about an apparent degredation of service with API-NG on Saturday afternoons.

My Test Application rarely requests more than 2 horse races in the same listMarketBook request ... most of the time it's requesting only one market.

On most weekdays using API-NG the roundtrip for a listMarketBook call is in the range 45 - 55 millisecs, which compares reasonably with getMarketPricesCompressed in API6, which usually takes about 45 millis.

BUT, this afternoon (Saturday) and last Saturday API-NG was taking 80-90 millisecs for listMarketBook between about 13:00 and 15:00 ... probably just about acceptable, but, almost exactly on 15:00 (both Saturdays) the roundtrip started to slow down, until I gave up on it when it reached (approx) 160 millis+. I switched back to API6, and it was still happily doing its getMarketPricesCompressed in (approx) 45 millis.

Is this a temporary phenomenon, something to do with API-NG being still, more or less, experimental, or is it likely to be a long-term issue?

[mja]

That's interesting. I was also running a test application today and saw much less change this afternoon.

I generally call listMarketBook for about 5 football markets with the average roundtrip time about 30ms. This slowed to about 40ms on average between about 2pm and 5pm but it was not obviously worse at 3pm.