Forum Discussion
Altera_Forum
Honored Contributor
12 years agoYou can get an idea of what Quartus thinks it did on the "Flow Elapsed Time" report. I see 2.9 Average Processor Used by the Fitter process. And if you're watching your system through the process, you can see processor utilization for the 'fitter' executable peak at some multiple maybe %450 (average 4.5 CPU core used during given time interval). Analysis and Synthesis, Assembler, Netlist Writer are all single threaded (1.0 CPU used) and unfortunately in my case account for >%50 elapsed time.
That said, hussainw, there is no way you are going to stress a 16-core machine by running a single instance of Quartus. If you want to speed things up, I think you need to look into design partitions and parallel builds or at least incremental compilation to avoid recompiling unchanged files.