Benchmarks in the Godot demo project (Godot vs NumDot)

[Ivorforce]

These benchmarks should compare performance you would normally get with godot vs performance you can get with NumDot.

Ideally, they

• Are separated into several functions, so only a few can be run
• Generate results files we can regularly upload somewhere
• Test several configurations of run times vs. load sizes.
• Somebody commented tips for this in my reddit thread

Not all of this is needed for the initial benchmarks. Even just a few proper benchmarks would be helpful.

Godot has a benchmark repo we can pick math-y benchmarks from, to compare to: https://github.com/godotengine/godot-benchmarks/tree/main/benchmarks

[Ivorforce]

I implemented two benchmarks:

• The sieve of eratosthenes (finding primes)
  • NumDot wins by ~16x
• Generating a regular polygon
  • NumDot loses by ~10x

The second benchmark is bottlenecked mostly by needing to convert to Packed*. That would be improved a lot by implementing #42 and #62. Good goals to be set!

Edit: The bottleneck has been resolved, it's now roundabout on par!

[Ivorforce]

We should add a benchmark generator for all common functions (in addition to hand-written ones). Most current benchmarks are very tiresome to implement, and end up just creating an array and calling a function in a loop. We can automate that, and add benchmarks automatically for every function! This would also be nice in case someone wants to quickly check other combinations of functions.