the old problem remains and I dont know what to do:
today I had 20 sec refresh (idle and inplay), 20 api-calls, no trigger logs on, no other program running.
and then, at 20:45, when all eng second league and italy serie b games were beginning and ca. 70 markets were monitored at the same time, cpu goes up to 100% for some moments, then to 30-50%, and about 20-30% of the bets were NOT placed.
any idea? (I have no firewall and no antivirus that could make problems). I cant imagine that no one else has a problem with the cpu und placing bets. 70 markets are huge, but not soooo much. and some triggers are nothing, could be also 20-30-50 triggers on 100 markets - and that creates problems? cant believe that everyone is working with only 2 and a half triggers on only 5 markets..
and cant believe that even a cpu-usage of 100% for some moments avoids placing bets, that should not be in any case. what is the problem to keep the bets in the memory? after some milliseconds mfp should place them..
any idea, any help, any explanation, any similar experience? if not, I will give up and ask for returning of the six month already paid.
1 unhappy user. thx anyway.