Quote from: houseworx on January 22, 2018, 07:39:10 PM

Quote from: seuntjie on January 22, 2018, 07:16:18 PM

What could be happening here is the "optimizer" is killing processes that use the internet frequently and a lot of it, like windows updater or other applications that perform automatic updates/update checks. If the bot has access to a larger part of your total network throughput, it will run more stable, faster and use more CPU,ram and disk resources because it has to process more bets.

Giving the bot more CPU power won't make it more stable or let it run faster (unless you're on like a single core 1ghz machine), because 99% of the time the bottleneck is your network and the sites bet throttling.

If you want to find out what the maximum betting speed of the bot is on your PC, run a simulation of 1000 bets and time it, then take the total seconds it took the simulation to run and divide it by 1000. (even on a very crappy PC, this should be at least 25) If you're betting at a site and the betting is slower than that, it's your network, the throttling or the site.

maybe you can give a hint, how to run simulation at all properly? because 98% of a time, when i run sim from console, with any kind of script, even "base default" what is on code place, when dicebot are turned on? all time after first 2-3second i get "dicebot has stopped working" bla bla bla, and closing program automatically. there is no matter if it old, or new version, tryd to reinstall with fresh one etc, nothing help, maybe 1 time of 50, i im getting runsim worked and dont crush. Sad

now i want to test this kind ot thing about "betting speed for each pc" what you given upper

That usually happens because I haven't implemented the provably fair functions of the site you have selected. Try selecting another site before starting the simulation, like primedice for example.