http://robowiki.net/w/index.php?action=history&feed=atom&title=Thread%3ATalk%3ASlowBot%2FDecision_Speed_OptimisationThread:Talk:SlowBot/Decision Speed Optimisation - Revision history2026-04-28T19:49:57ZRevision history for this page on the wikiMediaWiki 1.34.1http://robowiki.net/w/index.php?title=Thread:Talk:SlowBot/Decision_Speed_Optimisation&diff=30599&oldid=prevSkilgannon: New thread: Decision Speed Optimisation2013-05-05T13:09:47Z<p>New thread: Decision Speed Optimisation</p>
<p><b>New page</b></p><div>I was playing around with a speed comparison with manual point-in-field checks to the Rectangle2D.Double.contains(x,y) method, and discovered that if I used && between the booleans I got pretty much exactly the same speed, but if I use & I get double the speed and exactly the same result. I'm guessing this is due to my CPU being able to evaluate multiple boolean expressions simultaneously, but if && is used only one is allowed to be executed at a time, or perhaps & just allows the pipelines to stay more full because there is less branching. <br />
<br />
Of course, there are some reasons you might want && instead, like null checking before examining an object property, and && is smaller codesize for those bots that are codesize restricted, but particularly for high-load situations like the inside of precise prediction or play-it-forward loops, using & for your decisions might gain you some speed =)</div>Skilgannon