I see. So it is your test method that is useless because of internal optimizations, as was mentioned above.
You can have the same effect with Xojo. Insert the “speed” pragmas, compile it with aggressive optimisation, do a test.
Make the code loop 10, 100, 1000 times more often.
Recompile. Test again.
There will be no difference in execution speed except for system load differences. I bet Java does the same optimizations on standard settings.
2 Likes
Java optimized 9 microseconds and xojo above 50 microseconds. This discussion is useless cause the xojo without pragmatic is running nearly a minute as you can read so for your understanding: xojo needs with pragmatic between 58 and 59 microseconds. Java 9. end of discussion