by Gavin » Sat Jan 24, 2015 12:25 pm
Hi playpower,
My guess is that some of your in-play orders have been reaching the timeout setting of 10 seconds and this may have caused them fail, or to briefly look like they failed.
The PlaceOrders calls is the API call used to send bets. Your maximum duration for that is just over 10 seconds (10894ms), which is so similar to the 10000 timeout that I think they have hit the timeout. Assuming the in-play delay of the markets you trade is 8 seconds (8000ms), this implies that your orders were delayed by a bottleneck.
Please amend your Exchange Timeout number to 20000 (go to Settings | API Refresh, then you'll find it near the bottom of the page). Originally this number was set to 10000, but I recommend you to change it to 20000 or even 30000. This will ensure that if your orders are a little bit delayed (for example beyond the usual 8 seconds in-play delay for some soccer matches), that they will still proceed normally and not be timeout. Thus, they won't timeout until 20 seconds, at which point you probably really want them to timeout anyway.
Otherwise, your ApiMonitor stats don't look too bad. The main data refresh API call is ListMarketBook, for which you have an average duration of 141ms which is in the normal range. However your maximum duration of that call has occassionally reached 5051ms, during brief moments when there is a bottleneck, but this is not too concerning because it has only been only 750ms (threshold two) on 14 occassions which was on a mere 0,2076% of the calls. I would not be too concerned by those numbers, because the occassional internet or network slow down is inevitable. However you should try using slightly bigger refresh intervals, just to see if those stats can be made even more perfect and bottlenecks reduced even further. By using bigger refresh intervals you are putting less pressure on the internet connection, so when there is a bottleneck you will recover from it more easily by not adding extra pressure to the bottleneck. Reducing bottlenecks in ListMarketBook will help to ensure that your internet route is not congested. When it is congested it will also slow down the placing of bets. However your internet is only very rarely congested so if you can't improve it then don't worry. There is also a maximum concurrency setting (also in the API refresh tab in setting), this is set to 5, so if the calls are slow to return then you won't keep sending more calls once 5 have not yet returned. So another way to reduce pressure on the internet connection is to reduce this number, say from 5 to 3, but usually it is fine to just leave it at 5 and instead concentrate on using a slightly bigger refresh interval in order to avoid the bottleneck in the first place.
Kind regards,
Gavin
