The-OpenROAD-Project/OpenROAD
Vedi su GitHubLong running OR commands should report their runtime
Open
Aperta il 26 apr 2024
good first issue
Descrizione
Description
Every “long running” command should report how long it took to run it. The goal would be to be able to easily compare log files from different runs. E.g. vimdiff dir[12]/log or grep runtime dir2/log > dir2/runtime diff dir[12]/runtime
Suggested Solution
Currently there seems to be a way to get ORFS to report runtime and memory usage. But this relies on running the openroad executable for each and every step. And it's not "built into" openroad, it relies on external scripting. It should be possible to have one OR tcl script to run "the whole flow" and still get this information in the log.
Log Elapsed seconds Peak Memory/KB
1_1_yosys 243 971412
2_1_floorplan 27 510688
2_2_floorplan_io 4 363812
2_3_floorplan_tdms 4 362360
2_4_floorplan_macro 4 367364
2_5_floorplan_tapcell 4 325804
2_6_floorplan_pdn 6 381020
3_1_place_gp_skip_io 38 461672
3_2_place_iop 4 372996
3_3_place_gp 613 1048224
3_4_place_resized 94 602152
3_5_place_dp 78 657092
4_1_cts 152 747132
5_1_grt 6137 1298604
5_2_fillcell 5 494576
5_3_route 543 11470100
6_1_merge 15 815860
6_report 198 2751824
Total 8169 11470100
Additional Context
No response