(06-09-2022, 09:07 PM)DSMan195276 Wrote: Yes, you should expect longer compilation times when enabling optimization. For larger QB64 programs this can be quite a bit longer. It is possible to improve the compilation times but I wouldn't expect that any time soon since it would require some fairly fundamental changes to how QB64 generates the C++ program.
Cool, that explains it. I tried the optimization enabled, and it made a significant difference in number crunching speed. Compilation times are extended somewhat, but depend on how long the program is. In shorter programs, I don't notice much difference. Maybe those with gymongous programs will notice more.
I have a number crunching test I wrote, which spits out prime numbers, starting with 3. It does so in groups of five trials each, 3 to 100,003, 3 to 150,001, 3 to 200,003, 3 to 300,007, and 3 to 400,009.
For the speed test, of course, it doesn't display all the primes, only displays the last one.
Oddly, with version 0.8.0, without optimization, it seemed slightly slower than version 0.7.0. In my PC, to reach 400,009 took about 0.87 to 0.93 seconds at most, with version 0.7.0. But with version 0.8.0 without optimization, a couple of times it took just over 1.0 sec.
With optimization enabled, instead, we're down to a range of 0.61 to 0.66 seconds, shortest to longest time required of the five trials, to reach 400,009. A real improvement.
Roughly what has happened is, each of those groups of results, with optimization enabled, show about the same time required as the shorter group of tests did before. So, the time it takes to reach 400,009 is about the same as it required previously to reach 300,007. Similarly, the times required to reach 200,003 are about the same as it took previously to reach 150,001. Slick! Thanks!
(Parenthetically, a BIOS update maybe 2 years ago improved this particular test quite a bit too. In my own 6th gen Intel Core i7, performance went down when they did the first BIOS change to mitigate the specter/meltdown threat. But then they more than compensated for that performance loss with a BIOS update some time ago, maybe at most 2 years ago. Saying this for those guys who refuse to update their BIOS!)