Honestly... that doesn't seem like it has optimised anything. If anything, it looks like it is just putting your CPU under extra load... for no real reason. 
I'm always very skeptical about these "optimisation" apps. If DiceBot was only driving the CPU to 30%, then it would appear that there was no need to optimise anything, the bot was not being bottlenecked by your CPU and would have been running as fast as possible. If however, the CPU usage had been maxed at 100% then there was likely some bottlenecking occurring and there might have been room for improvement.
In any case, the likelihood of this app having any effect on DiceBot is relatively small. The overriding factors that will control how fast the bot is able to bet are the latency to the betting site and the size of your bets (most sites prioritise larger bets). RAM and how long the bot has been running have a secondary effect if you have all the graphs/charts on
I'm always very skeptical about these "optimisation" apps. If DiceBot was only driving the CPU to 30%, then it would appear that there was no need to optimise anything, the bot was not being bottlenecked by your CPU and would have been running as fast as possible. If however, the CPU usage had been maxed at 100% then there was likely some bottlenecking occurring and there might have been room for improvement.
In any case, the likelihood of this app having any effect on DiceBot is relatively small. The overriding factors that will control how fast the bot is able to bet are the latency to the betting site and the size of your bets (most sites prioritise larger bets). RAM and how long the bot has been running have a secondary effect if you have all the graphs/charts on