Data Useage

Discuss anything related to using the program (eg. triggered betting tactics)

Moderator: 2020vision

Data Useage

Postby Fixador » Wed Dec 18, 2013 10:00 pm

Before I get into trouble again with BF, this is a request for some advise before I pose the following question to BF:-

after reading http://www.betfair.com/aboutUs/Betfair.Charges/%20%20section%205 I have been counting on my fingers as follows:-

What I am considering doing is as follows:-

To have upto 6 markets (tabs in BA and Excel ) open simultaneously - all UK horse racing ( I cant remeber if there has ever been actually as many 6 afternoon venues of UK horse racing - I dont do evening start venues - ie first race after 6 pm ). Anyway, I am assuming 6 venues, ie 6 markets simultaneously open.

Assuming a worst case - the racing scheduled start times are 5 mins apart ( its a saturday ! )

My basic refresh rate for each market is once per second - ie, 2 data requests/second

But, in any 5 min period - one of the markets will have its refresh rate increased to 5 per second for approximately 30 seconds ( worst case - I hope ) during part of the 'in-running' period.

So, in the 30 second period - I reckon my requests are:-

5 markets at 2 data requests/second each = 10 data requests/second

1 market at 10 data requests/second = 10 data requests/second

So for 30 seconds in a 5 minute period my max request rate = 20 data requests/second ........... right on the limit !

However, at any one time, some of these markets are going to be 'closed' - the data request rate on a closed market is ??????????

That's the end of the question at the moment - well as much as much as my addled brain can cope with. I realize there is more in section 5 - as relates to the average data requests over an hour.

So, I suppose another question is - should I reduce my basic request rate down from 1 refresh per second to say 0.75 refreshes per second - to stay well away from the data useage limit ?

Thanks for reading. Fixy
Fixador
 
Posts: 322
Joined: Mon Apr 23, 2007 9:24 am

Postby alrodopial » Wed Dec 18, 2013 10:34 pm

I have my limit set to 30/sec because the limit increases by the bets I place.
I dont think I even reach this new limit
Based on your risked amounts the requests can increase greatly.
Decrease your refresh rate to 0.5 per sec while increasing the max to 30/sec for a day.
I dont think you will have any problem
Just check it for a day
alrodopial
 
Posts: 1384
Joined: Wed Dec 06, 2006 9:59 pm

Postby Captain Sensible » Thu Dec 19, 2013 3:47 pm

Under the Account tab on Gruss there's a selection called 'Calculate Data Requests Allowed' check that out as if you're quite active with your betting you'll most likely pay a fair amount of commission and that really racks up the requests you can use. I regularly go over the limits but my commission always offsets any data and transaction costs
User avatar
Captain Sensible
 
Posts: 2923
Joined: Sat Nov 19, 2005 2:29 pm

Postby Fixador » Thu Dec 19, 2013 7:39 pm

Thanks guys for the input - might be a while getting to grips properly with this.

I am just about ready to give it a whirl tomorrow - fingers crossed I have all of the code bugs out now.

More queries to follow no doubt.....
Fixador
 
Posts: 322
Joined: Mon Apr 23, 2007 9:24 am

Postby wizardofmann » Fri Dec 20, 2013 10:04 am

I am fairly new to using Gruss software. I have not dared to mess with the throttling/data requests after watching the tutorials, so it is still set to the default of 10 date requests per second.

I only bet on UK/Irish horse racing and never place more than 40 bets per hour. I have carefully read the Betfair charges section but I am still none the wiser as to what the maximum requests I could set the throttling to. If someone would be kind enough to advise me on this I would be forever grateful.

I thank you in advance.
Never say never
wizardofmann
 
Posts: 166
Joined: Tue Jul 23, 2013 2:43 pm
Location: Isle of Mann

Postby milfor » Fri Dec 20, 2013 11:41 am

Don't mix up transaction charge for bets and data charge for requests.
You can make 1000 bets per hour (only 333 if they are below £2).
You can set the throttling to 20 if you only have 1 Gruss open and don't use other accesses to Betfair at the same time.
milfor
 
Posts: 437
Joined: Mon Jun 26, 2006 1:44 am

Postby wizardofmann » Fri Dec 20, 2013 12:04 pm

Thank you very much milfor. Yes I only use 1 Gruss. By accesses I presume you mean I don't have the Betfair site open as well?
Never say never
wizardofmann
 
Posts: 166
Joined: Tue Jul 23, 2013 2:43 pm
Location: Isle of Mann

Postby milfor » Fri Dec 20, 2013 3:10 pm

If you have the Betfair site open and a script refreshes every second then
this would be a problem. If you have the Betfair site open and you only
refresh manually then it's no problem.
milfor
 
Posts: 437
Joined: Mon Jun 26, 2006 1:44 am

Postby wizardofmann » Fri Dec 20, 2013 6:31 pm

Thanks again milfor and most appreciate your input :)
Never say never
wizardofmann
 
Posts: 166
Joined: Tue Jul 23, 2013 2:43 pm
Location: Isle of Mann


Return to Discussion

Who is online

Users browsing this forum: No registered users and 70 guests

Sports betting software from Gruss Software


The strength of Gruss Software is that it’s been designed by one of you, a frustrated sports punter, and then developed by listening to dozens of like-minded enthusiasts.

Gruss is owned and run by brothers Gary and Mark Russell. Gary discovered Betfair in 2004 and soon realised that using bespoke software to place bets was much more efficient than merely placing them through the website.

Gary built his own software and then enhanced its features after trialling it through other Betfair users and reacting to their improvement ideas, something that still happens today.

He started making a small monthly charge so he could work on it full-time and then recruited Mark to help develop the products and Gruss Software was born.

We think it’s the best of its kind and so do a lot of our customers. But you can never stand still in this game and we’ll continue to improve the software if any more great ideas emerge.