Aggressive, Moderate, Default Benchmark Report

How much benefit from different Build options?

The same Desktop Xojo 2023R3 code with the same test data (100 million data points) on a dedicated Windows 10 PC with no Internet connection and no user interaction. Here are the times for computation:

Default Build: 2 hours 50 minutes
Moderate Build: 1 hour 59 minutes
Aggressive Build: 1 hour 49 minutes

And for comparison with similar code and the same data:
Compiled VB6: 2 hours 18 minutes
Intel Fortran: 0 hours 48 minutes

Does your Xojo code have the same trend?

1 Like

Hi Mike! I’ve also seen huge improvements in my apps but I’ve been to lazy so far to measure the numbers :wink:
Do you have pragmas in your methods like:

#pragma BoundsChecking        false
#pragma StackOverflowChecking false
#pragma NilObjectChecking     false

These can also bring a big performance gain.

Thanks, Carsten. No pragmas yet as the code is at the beta-test stage.

@Mike_Linacre1 if you are in the Betas/Testers group, would be intersting to see your tests on the newest Xojo prerelease versions…

2 Likes

Your results are going to depend on what you’re doing and how you code it. It’s possible to defeat certain optimizations.

Thanks Mike D. - have now requested to join the Xojo Testers group.

With the computationally-intensive methods in a thread with Priority 20:
Moderate Build 2 hours 14 minutes
So allowing more user-responsiveness cost about 13% extra execution time: Yes, probably worth it.