Interval Heap vs MinHeap
Fragment of a discussion from User talk:Rednaxela/kD-Tree
← Thread:User talk:Rednaxela/kD-Tree/Interval Heap vs MinHeap/reply (3)
Jump to navigation
Jump to search
← Thread:User talk:Rednaxela/kD-Tree/Interval Heap vs MinHeap/reply (3)
Just tried that. The pruning is still not paying off compared to the extra overhead of the IntervalHeap.
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:Rednaxela/kD-Tree/Interval Heap vs MinHeap/reply (4).
I was thinking it was the different heap... but actually turns out the heaps are approximately the same performance, with the difference being the pruning:
- #1 Rednaxela's kd-tree (3rd gen, Interval Heap) [0.0290] - #2 Rednaxela's kd-tree (3rd gen) [0.0290] - #3 Rednaxela's kd-tree (3rd gen, Interval Heap, Prune When Points Added) [0.0293] - #4 Rednaxela's kd-tree (3rd gen, Interval Heap, Avoid Growing Heap When Possible) [0.0294] - #5 Skilgannon's Cache-hit KDTree [0.0296]
So the incremental difference from a larger heap is less than the cost of removing the points.
Skilgannon (talk)