It's keeping up well, and when it hits a wave of confirmation, it races ahead very rapidly on low CPU (since that's largely sequential). And I've noticed that as the tables grown, the spent query slows down materially relative to the others. This is the exhaustive hashmap search.