-
Notifications
You must be signed in to change notification settings - Fork 536
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
Improve incremental repair running times so that megaboom can be done in 24 hours #5725
Comments
after 8 hours or so, the stack trace is the below... Hmm.... throw is used to abandon things when searching for a solution, could this be done without exceptions to improve performance?
|
@jeffng-or @precisionmoon @maliberty In addition to improving performance, can we add some logic to abandon futile repair timing automatically? WNS is -3812.590ps for 3000ps clock period. Isn't repair_timing an exercise in futility at that point? |
I continues as long as there is some progress, not based on the clock period. |
Description
repair_timing breaks the 24 hour budget for megaboom, so repair_timing has been disabled.
Note that repair_timing is not the biggest problem in megaboom(the clock period is ca. 3000ps now and I believe repair timing is a small fraction of that...), so this is a forward looking feature request to when macro placement has been addressed.
Untar https://drive.google.com/file/d/14-UYL5iUD1GWlL10sYCOPIB0jOpVYDzd/view?usp=sharing
Suggested Solution
Make repair_timing faster
Additional Context
No response
The text was updated successfully, but these errors were encountered: