Hi Evan, I made a test on my new mini PC, (MinisForum EliteMini AI 370), and the full compilation tests of the demo folder took more or less 45 minutes. Certainly with more powerfull processors shorter times can be reached. But I am uncertain, because during compilation process, the AMD AI 370 processor worked only less than 15%. What can be the bottleneck of the compilation tests ?
Good question. We could Sum the compile time and then deduct that from the total time ( end to end time ) to give Batch processing time. Then, we could add -QUIET command to the compiler to remove all dialogs ( that is surely one bottle neck ). That would leave just the compiler processing. Removing some of syntax checking ( during this test only ) would improve performance - as this is essentially text string manipulation and this is 'slow'. After those changes... the speed is now the internal list access process within the compiler. Something to look at next year.
Hi Evan, I made a test on my new mini PC, (MinisForum EliteMini AI 370), and the full compilation tests of the demo folder took more or less 45 minutes.
Certainly with more powerfull processors shorter times can be reached. But I am uncertain, because during compilation process, the AMD AI 370 processor worked only less than 15%.
What can be the bottleneck of the compilation tests ?
Good question. We could Sum the compile time and then deduct that from the total time ( end to end time ) to give Batch processing time.
Then, we could add -QUIET command to the compiler to remove all dialogs ( that is surely one bottle neck ).
That would leave just the compiler processing. Removing some of syntax checking ( during this test only ) would improve performance - as this is essentially text string manipulation and this is 'slow'.
After those changes... the speed is now the internal list access process within the compiler.
Something to look at next year.
Good Day Evan, I just send you a message on Google Chat about the tests.