@Matt Liberty: Question: I was running a largish user project job on openlane, and I noticed that (1) all steps used only one processor core, except for detailed routing, and that used only two cores; and (2) detailed routing sucked up memory until it exceeded my 16GBs and then the process got killed. For (1), are there parameters that define parallelism that exist but are not being used by openlane? And for (2), is that an inevitability of the detailed router, or is there a way to force it to keep memory usage under a given amount?