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.
#define guarded change to modify router loop exit behavior (not enabled by default). Instead of exiting at max_router_iterations, if IGNORE_ITERATION_LIMIT_HEAP_PUSH_FACTOR is defined, the router will continue to run iterations if the number of heap pushes per iteration is less than the average number of heap pushes per iteration by the factor specified.
Motivation and Context
With a hard iteration limit, sometimes the router aborts even though it appears to be converging because it is down to only a few overused nodes. When the number of heap pushes per iteration is small, each iteration runs quickly relative to earlier iterations, so it may be advantageous to let the router continue in the hopes that with a little extra time, the router will converge.
This change is guarded so that further evaluation can be done (over a period of time) in the context of other VTR experiments. If the change is generally helpful, then we might want to enable it by default -- though finding a clean way to do it might require some thought as simply ignoring max_router_iterations can be confusing.
Types of changes
Checklist: