Closed isaacsas closed 1 year ago
My only confusion is to why this issue has cropped up now all of a sudden.
This popped up when v1.9 came out.
Huh, I never saw that issue before (even with the previous PR tests passed).
In any case I did dig into it with the allocations profiler and it seemed to be coming from additional push!
s into groups within the priority table as best I could tell (and not the function wrapper type instability issue we had before). Moving this test to use StableRNGs
should hopefully eliminate the issue.
It seems that it currently takes a couple runs of RSSACR before the table allocations are fully settled down now. It is expected that there can be some allocation differences here for the algorithms that use PriorityTables (which can dynamically allocate additional buckets, but only ever grow, so should settled down eventually).