Cache the set of active transfers in receive arbiter #319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
receive_arbiter
tracks atransfer
for every transfer id it learns through an inbound pilot, so long-running programs likewave_sim -T 10000
will fill the transfer map quickly. It's anunordered_map
so lookups shouldn't suffer, but we iterate over it inpoll_communicator
, which has linear complexity (initially found by @psalz).We only need to poll transfers for which we have already seen the
receive_instruction
. This PR avoids the linear growth by caching the set of active transfers in a vector, and iterating over that.I've used the opportunity to refactor the code a bit and use
std::erase_if
in the many places we had erase-remove idiom before.