Open thebyrd opened 3 days ago
Try enabling virtual memory. As I recall, reducing number of cores wont help much.
This is a large design:
Number of components: 9212750
Number of nets: 1942672
though it is a bit odd that you have so many more components. Does this design have a lot of dead space? I doubt your problem relates to constraints.
I added 30GB of swap and the same thing happened, it just took longer. I'm also running it on an ec2 instance with 124GB of Ram and that's still running. What were the specs of the machine you confirmed it worked on?
Elapsed time: 3:45:22[h:]min:sec. CPU time: user 230047.12 sys 2971.37 (1723%). Peak memory: 63405600KB.
What you want to know, how much vm is required, should be possible to measure with https://github.com/The-OpenROAD-Project/OpenROAD/pull/5260
I checked: I have 256GB vm, 64gb ram and 48 cores(96 threads).
@thebyrd FYI https://github.com/The-OpenROAD-Project/megaboom/pull/66. Running a build now to test...
During CPUHeavyGenrule //:BoomTile_route, openroad is being killed by the OOM killer. Which constraints can I change so this will consume less memory? I appreciate that this can be fixed by just getting more RAM, but my current machine has 64 GiB of RAM. Its a 20 core i7 running Ubuntu 22.04.4 LTS