KDTreeF
Fragment of a discussion from User talk:Chase-san/Kd-Tree
← Thread:User talk:Chase-san/Kd-Tree/KDTreeF/reply
Jump to navigation
Jump to search
← Thread:User talk:Chase-san/Kd-Tree/KDTreeF/reply
Nice stuff! With that graph, it looks like the place you have the most room to squeeze out more performance if you wish to, is by refactoring the code so that the JIT gets it optimized sooner. Having the lowest time in those first few searches is certainly neat, and perhaps is the most important thing in the robocode context as that's the most likely time for a kd-tree to lead to a skipped turn. I wonder what it took to get that down and how much that is dataset specific.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:User talk:Chase-san/Kd-Tree/KDTreeF/reply (2).