-
Notifications
You must be signed in to change notification settings - Fork 418
Congestion-Aware Initial Accumulated Cost #3031
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ted_routing_util()
… t_route_opts check if ExtendedMapLookahead fails
To-do list
|
titan_quick_qor
In experiments with a channel width of 250, |
VTR benchmarks minimum channel width search
Minimum channel width was reduced in two circuits. |
VTR benchmarks
|
Looks good, thanks. We should get koios as well, since this is a big change. |
W=300
|
vtr_reg_nightly_test7/3d_sb_titan_other_auto_bb
|
vtr_reg_nightly_test7/3d_cb_titan_other_auto_bb
|
vtr_reg_nightly_test7/vtr_reg_qor_large_run_flat
|
@vaughnbetz |
Please summarize where we see benefits, and take a look at the minimum channel width results (cpu time is up --> just the two circuits with better results?) |
The minimum channel width is reduced for both When the channel width is low enough to cause congestion, routing converges faster if the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some testing for --route, and think about whether the state transfer from place->route would be cleaner if the router loaded everything.
When the placement was read from a file, NetCostHandler was never read, and channel util estimate was never computed. RoutingChanUtilEstimator computes BBs in the routing stage and calculates channel utilization there
…stion_threshold and router_initial_acc_cost_chan_congestion_weight
This PR adds a new option to bias routing away from congested channels during early iterations by adjusting the initial accumulated cost based on estimated CHANX/CHANY utilization.