Hi
I think you are going to struggle a bit on this one. Ideally, you want the list of bets to be updated before the trigger repeats again, so you can use selection variables. Problem is your total RPS will go sky high. Now the data monitor will throttle these, but in doing so will queue the requests, making it inefficient. The key to this method has to be that the bets are updated before the trigger repeats, say: update bets 0.2, trigger no more often than: 0.5
Switch off everything that you don’t need to give all the RPS to the task in hand, though I’m sceptical that the software will handle this.
Another idea to look at (but I think this will work for ALL selections, not a selection) is the Data Request Monitor:
Set the Timeframe setting to 3 seconds
Trigger condition:
Trigger Expression mntr_trans_number is equal to 0
The thinking here is the data monitor should record a transaction long before the list of bets is updated etc.
Out of interest are you using a VPS?