this is surely the best option.
churn will occur locally in time and space. In any case we do no want to support any churn-mitigation among threads!