Results Log Updates (possibly) and some major delay problems

Please post any questions regarding the program here.

Moderator: 2020vision

Results Log Updates (possibly) and some major delay problems

Postby laffo16 » Tue Oct 21, 2008 4:39 am

i have been placing a large number of bets in excel recently. seeing that the more bets i place through excel the longer it takes for the Bet Results Log to update, so i have automated the task of deleting the results log using the -7 trigger at specific points to help speed up the process of the -6 call. however i have found that after calling -7 and deleteing the log, this does not effect the time it takes to call -6, the time remains pretty much the same as it did before.

so i tried disconnecting the workbook and reconnect logging. but this makes no difference to the time also. the only way i can reset this trigger to its default speed is to close and relaunch BA. so i ask, is it possible that you could increase the speed of this trigger so that it performs just as fast as it would on a newly opened BA spread sheet logging (after a -7 call).

i'm presumming that the results are still being requested from betfair but just not being displayed on the log after a -7 call, which maybe the cause of the bog down. after around 200 bets and a -7 call, it can still take 10-15 seconds to updates the results log.

your thoughts on this pls gary, many thanks, laffo16

-----------------------------------------

after further testing, i understand that the results maybe parsed from one of betfairs webpages, im now unsure wether it was the quantity of bets which was slowing down this call or wether it was lag in downloading the webpage. i experianced a problem yesterday when my bot thought it had reached the last race as the next race failed to load in excel, being at the begining of the day with a list of races still in the quick pick list this was no the case. the timeout period for my bot for the next track failing to load would have needed to have been 3 minutes or more (so this meaning excel failed to load the new track after 3 mins). i wasnt around at the time and didnt see this happen.

today i noticed that after chaning courses (-1 trig), the market loads first in BA but it can sometimes take a very long time before excel is updated (like several minutes). i thought hmmm maybe the results log update request is cause the major lag here too.

so now i'm wondering if any else out their has experianced simular heavy delays during excel updating between markets or during a results log update. (not between 5-15 seconds, but much longer, like a minute or more)

if results log update drag is the cause, perhaps a timeout or a failed response would be good. admin help?
User avatar
laffo16
 
Posts: 172
Joined: Sun Jan 27, 2008 6:52 pm

Postby GaryRussell » Tue Oct 21, 2008 7:33 am

I will look into this asap.
User avatar
GaryRussell
Site Admin
 
Posts: 9871
Joined: Fri Nov 18, 2005 8:09 pm
Location: Birmingham, UK

Postby GaryRussell » Thu Oct 23, 2008 9:08 am

I think it's the requests timing out due to problems with Betfair's server or somewhere along the route. A lot of users have been experiencing problems with sticky refreshes.

When the program switches races it first tries to log the bet results, if this fails then the Excel update is aborted. If the requests timeout, currently set to 1 minute then it will be 1 minute before the next attempt so it could be caught in a loop of 1 minute timeouts. There is a further problem if there is an interruption after it starts receiving data, the timeout for receiving data is 5 minutes!

The program does not scrape a web page to get these results it uses getMUBetsLite in batches of 20 therefore 10 requests for 200 bets. It also uses getAccountStatement. So for 200 bets are 11 requests so there will be issues if any of the responses are slow. I don't know why I made it batches of 20, it can be batches of 200. I will release an update later today.

In summary I will release an update later today which will increase the batch size of getMUBetsLite to 200, decrease the read timeout from 1 minute to 30 seconds and decrease the write timeout from 5 minutes to 30 seconds. This should help.
User avatar
GaryRussell
Site Admin
 
Posts: 9871
Joined: Fri Nov 18, 2005 8:09 pm
Location: Birmingham, UK

Postby GaryRussell » Thu Oct 23, 2008 9:23 am

I have uploaded version 1.1.0.26, install it using the link below. You must first uninstall the current version using the control panel.

You probably don't need to clear the list with -6 now. Try it out and let me know if it has improved.

http://www.gruss-software.co.uk/Betting ... a_Test.msi
Last edited by GaryRussell on Thu Oct 23, 2008 11:29 am, edited 1 time in total.
User avatar
GaryRussell
Site Admin
 
Posts: 9871
Joined: Fri Nov 18, 2005 8:09 pm
Location: Birmingham, UK

Postby laffo16 » Thu Oct 23, 2008 11:18 am

wow thank you very muh gary, i'll let you know how it runs after a day or two of testin.
User avatar
laffo16
 
Posts: 172
Joined: Sun Jan 27, 2008 6:52 pm

Postby laffo16 » Tue Oct 28, 2008 4:22 pm

unable to test atm but i'll post my findings when i can
User avatar
laffo16
 
Posts: 172
Joined: Sun Jan 27, 2008 6:52 pm


Return to Help

Who is online

Users browsing this forum: No registered users and 51 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.