A Couple of Quick Questions

[KESIMKESIM]

Hi,

for a while now I've noticed Gruss freezing, whilst I can see BF site updating- it happens intermittently but always seems to happen in the last 10 mins or so before the off.

It happened again this pm on 3 out of 4 races I was having a dabble on.

In one instance over £70k was matched before Gruss re-synched. I doubt this is the API as more people would be complaining. I have a 'narrow' broadband service due to where I live which gives me about 450kb/s down/350kb/s upload speed, which normally works fine. I have assumed this to be the problem in the past.

I was wondering does Gruss need more bandwidth as there is more updating going on in the last 10 mins? I guess this will be linked to latency on the connection to BF. Are there any limits that I need to be aware of?

Does Gruss link directly to a BF server or does it connect to a Gruss server to access BF?

On a related point, when this happens, often but not always, my spreadsheet for triggered betting then fails to update when Gruss is once again updating and then will suddenly start again after a period where £10k or £20k further may have been matched.

Grateful, if someone could explain how Gruss links to and updates the spreadsheet such that I might understand what might be happening.

I use the Target.Columns.Count<>16 line in my code controlling the triggered betting. I can see Gruss odds, etc changing but my spreadsheet doesn't seem to be reacting at all.

Thanks for any advice and information.

[GaryRussell]

It doesn't download more data just before the off. The same amount of data is downloaded regardless of whether it is changing or not.

It links directly to Betfair's server. It would be against their T&C to do otherwise.

BA updates the prices and list of bets independently, but will not update Excel if the last bet refresh has failed. You may see prices updating in BA, but if the bet refresh request takes a while to get a response it will not update Excel.

Latency might be an issue for you. Try adjusting the timeout settings in Options|Performance Options menu. Untick auto adjust and set the timeout values to 500ms. Let me know if this helps.

[KESIMKESIM]

Thanks Gary for prompt reply.

I had never looked at the Performance Options screen before. Interestingly it had automatically set the Bet and Price refresh to over 1000ms already, which presumably indicates a problem with the time its taking to get refreshes due to the broadband link. Unfortunately, there's not much I can do about the broadband as I'm at the end of a 14km line - other than move house!

If I increase these to 2000ms does this mean Gruss allows upto 2 secs before it considers that the refresh has failed?

Thanks.

[GaryRussell]

That is correct. It does sound like latency is an issue for you unfortunately. You will probably benefit from having the auto adjust off because it's always trying to adjust it down to 200ms over time and will actually cause more timeouts.