Excessive Data Requests

[pugs]

Sorry if this has been asked or discussed.

I load many markets in tabs and i balance the refresh rate of these markets with data request throttle settings. Quite often when i then place bets in several markets my “Req” can often max out. I do realise this is because many markets are now valued at 2 requests and just happen to be trying to refresh within that same second.

My question is.....Do excess data requests queue up? and refresh those markets the next second...........Or are they just chucked out? and those markets have to wait till the next scheduled refresh.........And then maybe once again not refresh.

Thanks for any response.

[GaryRussell]

The requests wait until they can make a request without going over the limit. For example if 0.5 seconds has elapsed and 20 requests have been made in that 0.5 seconds then the next request will wait 0.5 seconds and all other requests from other markets will wait while the current request is waiting 0.5 seconds. The requests are not discarded until the next refresh.

Also bets are not counted as requests and are not throttled, but the bets manager is refreshed immediately following a bet and is subject to throttling so there can appear to be a lag between the bet being placed and appearing in the bets manager.

[pugs]

Thanks Gary.

We all know the API can get a little bogged down at times, i just wanted to make sure i wasn’t causing any problems of my own by having my data throttle set too low.

Could i just confirm one more thing with you regarding how BA refreshes bets......

1 market in 1 tab with 1 second refresh and no bets = 1 request per second

1 market in 1 tab with 1 second refresh WITH bets = 2 requests per second

10 markets in 10 tabs with 1 second refresh WITH bets = 20 requests per second..........

......Or does BA refresh all bets as a bulk request? ie weighted 5 per request?

[GaryRussell]

1 market in 1 tab with 1 second refresh and no bets = 1 request per second

Correct, but the bets manager does refresh once every 10 seconds to pick up any bets placed outside of BA, therefore there will be 2 refreshes every 10th second.

1 market in 1 tab with 1 second refresh WITH bets = 2 requests per second

Correct

10 markets in 10 tabs with 1 second refresh WITH bets = 20 requests per second..........

Correct

......Or does BA refresh all bets as a bulk request? ie weighted 5 per request?

No, this does not happen, but it is worth considering as it has the potential to increase the number of price refreshes. I will be looking into this.

[GaryRussell]

Could you help me test a new feature? It's in the test version which can be downloaded from http://www.gruss-software.co.uk/Betting ... a_Test.msi

There is a new option on the account menu. 'Calculate data requests allowed'. You can select a date and it will show you how many requests you could have made based on the commission paid and implied commission of settled bets. The API does not provide the commission rate for bets that lost (implied commission) so it is estimated by reducing 5% by your current discount. I would be grateful if you could confirm if the implied commission appears to be correct.

[pugs]

Quote:
1 market in 1 tab with 1 second refresh and no bets = 1 request per second

Correct, but the bets manager does refresh once every 10 seconds to pick up any bets placed outside of BA, therefore there will be 2 refreshes every 10th second.

Many thanks Gary, i feel silly now

I could not understand why bets were being displayed by one BA on one pc, for what sometimes seemed an age before they appeared on my BA on my other pc, and i thought i was not allowing enough data requests on that machine. But as you explained above, these bets are being placed by my trigger program or by my other BA, so with the 10 second bet manager refresh plus my 6 second market refresh on that BA, it could be as much as 16 seconds between bets appearing on one BA and the other.

Implied commission, what’s that

Not sure exactly how they calculate but there are 2 juicy ones below.

Amount AV Odds com rate imp com Req earned
£-1059 2.06 4.70 £49.77 248850

£-1225.53 4.4
£-1865.12 5 4.70 £145.26 726299

The second one is 2 losing lay bets on 1 selection
[/quote]

[pugs]

Amount AV Odds com rate imp com Req earned
£-1059 2.06 4.70 £49.77 248850

£-1225.53 4.4
£-1865.12 5 4.70 £145.26 726299

[pugs]

Sorry Gary it keeps compressing the figures. If you can’t see them clearly i will repost.

And many thanks.

[GaryRussell]

Thanks for the feedback. Implied commission is calculated on your net losses instead of winnings so you can earn the right to make extra requests whether you are winning or losing, they just want you to bet It should be calculated at the commission rate you would expect to be charged at if you had net winnings.

[pugs]

Cheers Gary
The implied commission figures are spot on, i wasn’t sure without checking with the website how the bonus data requests are calculated.
And It was my poor attempt at a joke saying “Implied commission, what’s that”. Suggesting that I don’t place losing trades, but my 2 implied commission examples prove that things can and do occasionally go horribly wrong.

Thanks again for your help with the “Bets refresh”/”Data Request”, It just totally left my mind that the Assistant would not refresh bets until it knew there was bets to refresh, it must be time for a holiday