Thread history
Viewing a history listing
Time | User | Activity | Comment |
---|---|---|---|
07:52, 4 December 2013 | Chase-san (talk | contribs) | New reply created | (Reply to Speed vs RoboResearch) |
16:55, 30 December 2012 | MN (talk | contribs) | Comment text edited | |
16:55, 30 December 2012 | MN (talk | contribs) | New reply created | (Reply to Speed vs RoboResearch) |
01:46, 10 December 2012 | Skotty (talk | contribs) | New thread created |
I'm curious what kind of speed improvements people have seen, if anyone keeps track. Today, in the midst of developing my own UI for RoboRunner, I decided to do a test run to compare RoboRunner vs RoboResearch. I ran MC2K7 Fast Learning challenge against XanderCat 11.6. All data was cleared from the robots directory in both tests. 2 Threads in both cases. RoboResearch ran in 5:30. RoboRunner ran in 3:50. That's about a 30% speed improvement -- pretty dramatic. With dirty data directories where there is a lot of past data, I bet the speed difference would be an order of magnitude more significant. RoboResearch can get pretty slow starting up battles when you haven't cleared out the data for awhile. Results will vary based on the data directories and what kind of robots are being run, but regardless, I think anyone using RoboRunner will see a noticeable speed boost. Very nice.
RoboResearch has an annoying problem when bots print something in the console. The clients crash and the threads become stuck in paused mode. You have to recreate the clients manually. So, RoboResearch is a lot more than 30% slower.