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 (2)
Jump to navigation
Jump to search
← Thread:User talk:Rednaxela/kD-Tree/Interval Heap vs MinHeap/reply (2)
How about keeping a flag in your leaf node processing so that you only try pruning if you added a new item?
Skilgannon (talk)
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 (3).
And how about if you just use the IntervalHeap, but don't try any pruning? I'm curious whether the pruning is slow, or the different heap.
Skilgannon (talk)
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)