Something decidedly odd going on with Betfair, for a few days now.
In the 8pm at Wolves, the odds fell from 4.4 to 3.85 on NO volume...pennies really. It wasn't a volatile or thin market.
Recently Excel has been slowing down and BetAngel CPU usage has been jumping to figures over 95% (I recorded a few 99%'s). On Saturday in the big race the response rates slowed down to almost a crawl and looked like stopping altogether.
I don't know what the reason is for the overload situation although I suspect Betfair have made a few changes.
Anyone else notice anything?
Danger Signals
Hi Peter,PeterLe wrote:James
what version of Betangel are you using and in which mode?
I haven't seen anything unusual in terms of excessive CPU usage..although I did seem to think the prices were refreshing quicker today than previously
regards
Peter
I am on V1.36.0 although I have tried a few others in the past week*. Connection mode is 1.
*I have done several restores 30 days apart (3 in total) but the CPU usage reaches very high levels when racing is busy. Night meetings BA cpu usage is pretty normal. The other thing is the 2nd of the lower R panels (responsiveness when retrieving bets) can jump from a normal average of 46ish to over 400. Retrieving odds milliseconds is always normal (avge 46)
James
-
mbailey1705
- Posts: 41
- Joined: Sat Oct 05, 2013 10:25 am
Hi James,
I thought connection mode 1 was NON api.
I have always used mode 0 which I believe is default API mode.
Not sure how much slower mode 1 would be if at all but maybe worth you trying mode 0.
I thought connection mode 1 was NON api.
I have always used mode 0 which I believe is default API mode.
Not sure how much slower mode 1 would be if at all but maybe worth you trying mode 0.
Hi James,
Normally I would suggest troubleshooting by a process of elimination, ie go back to an older version of BA and/or spreadsheet etc until you can narrow it down to one of those components or the system it is running on, but I know your quite a methodical person; so I assume you've already done this?
Peter made a offer on here last week for people to try the new version 1.37 (beta?) in anticipation of the new API, so you could contact support to see if you can try it out.
Ive been running it for a few days now and its been rock solid for me.
Regards
Peter
Normally I would suggest troubleshooting by a process of elimination, ie go back to an older version of BA and/or spreadsheet etc until you can narrow it down to one of those components or the system it is running on, but I know your quite a methodical person; so I assume you've already done this?
Peter made a offer on here last week for people to try the new version 1.37 (beta?) in anticipation of the new API, so you could contact support to see if you can try it out.
Ive been running it for a few days now and its been rock solid for me.
Regards
Peter
Thanks MBailey, I typed that without looking. I have connection mode 0 (not 1 as I typed)... and you are correct.
Ty Peter. I am reloading BetAngel and Excel to see if that helps. The strange thing is that when I switch to a race BetAngel is using 25-50% CPU and when I start recording data in Excel, the CPU usage increases during the last 10 minutes to around 90% usage. If I leave it on in-play it can get to 99% CPU usage. When I switch to the next race the cpu goes back to 25-50%.
I went back to a few old Excel sheets that used to be fine (some of the 1000's I have!!) but the same problem happens.
Anyway will let you know how it runs with new versions reloaded
Many thanks
Ty Peter. I am reloading BetAngel and Excel to see if that helps. The strange thing is that when I switch to a race BetAngel is using 25-50% CPU and when I start recording data in Excel, the CPU usage increases during the last 10 minutes to around 90% usage. If I leave it on in-play it can get to 99% CPU usage. When I switch to the next race the cpu goes back to 25-50%.
I went back to a few old Excel sheets that used to be fine (some of the 1000's I have!!) but the same problem happens.
Anyway will let you know how it runs with new versions reloaded
Many thanks
Nope Peter, its on my home PC.
I don't want to tempt fate but the changes I made, reloading BA and Excel seemed to have had a very positive effect. I didn't trade all day but for all but one race the CPU usage didn't go over 50% and Excel was recording well with no delays. Apart from reloading BA and Excel, I also reset the communications values switching smoothing off. I will gradually add these again over the next few days.
If I had to guess where the problem lay it would be that the Excel macros became corrupted, somehow affecting BetAngel. Will report back if I encounter any other problems.
I don't want to tempt fate but the changes I made, reloading BA and Excel seemed to have had a very positive effect. I didn't trade all day but for all but one race the CPU usage didn't go over 50% and Excel was recording well with no delays. Apart from reloading BA and Excel, I also reset the communications values switching smoothing off. I will gradually add these again over the next few days.
If I had to guess where the problem lay it would be that the Excel macros became corrupted, somehow affecting BetAngel. Will report back if I encounter any other problems.
I noticed a similar slowdown problem (CPU approaching 100%) on the same days last week. Tuesday and Friday were worst.
I put it down to 3 factors
1. Slightly old laptop (Core 2 Duo, normally no problems though)
2. I use Switesh's Excel spreadsheet to log all data with some modifications to capture inplay data as well as pre-off. This increases the load on my machine significantly. (Inplay data changes more often thus imposing a higher load on both CPU and my connection)
3. Many races with 10+ runners (more runners = more data to process, not just for my laptop but for Betfairs own servers to handle).
No of races with 10+ runners:
Tuesday
Newcastle 7/8
Wolverhampton 6/8
Friday
Redcar 7/8
Newmarket 5/7
Cheltenham 4/7
Haydock 3/8 (5/8 with 8 runners)
I put it down to 3 factors
1. Slightly old laptop (Core 2 Duo, normally no problems though)
2. I use Switesh's Excel spreadsheet to log all data with some modifications to capture inplay data as well as pre-off. This increases the load on my machine significantly. (Inplay data changes more often thus imposing a higher load on both CPU and my connection)
3. Many races with 10+ runners (more runners = more data to process, not just for my laptop but for Betfairs own servers to handle).
No of races with 10+ runners:
Tuesday
Newcastle 7/8
Wolverhampton 6/8
Friday
Redcar 7/8
Newmarket 5/7
Cheltenham 4/7
Haydock 3/8 (5/8 with 8 runners)