Should the `run` scripts compile in ReleaseSafe instead of ReleaseFast?

[IntegratedQuantum]

Should the `run` scripts compile in ReleaseSafe instead of ReleaseFast?

[archbirdplus]

We can compile performance critical files separately, right?

[IntegratedQuantum]

No, not in an easy way. We can disable safety checks in performance critical functions with @setRuntimeSafety(false) though.
Also I should probably check if the performance impact even is that big.

[archbirdplus]

See also:

@setFloatMode(comptime mode: FloatMode) void
Changes the current scope's rules about how floating point operations are defined.
This is equivalent to -ffast-math in GCC```
Is this the only way to enable fast math?

[IntegratedQuantum]

I just compared the two release mode and loading a render distance 12 world goes from 33.5 s to 40 s, so a 20% increase in runtime.
Overall I'd say it's not too bad for the potential benefit it gets us. I would need to fix #410 first though.

[archbirdplus]

Can you profile with fast math and stuff?
Also, how do you profile Cubyz? I used this, but it feels like a hack.

if(self.size == 0) {
    if(main.game.world != null and main.game.world.?.gameTime.load(.monotonic) > 0)
        main.Window.c.glfwSetWindowShouldClose(main.Window.window,main.Window.c.GLFW_TRUE);
}

[IntegratedQuantum]

Also, how do you profile Cubyz?

In this case, I just used the timer of my phone xD

[archbirdplus]

Not sound :(
My hack is better. You can do time ./zig-out/bin/Cubyzig.

[IntegratedQuantum]

time is actually worse at measuring this, because it also measures the time that is spent in the menu.

[archbirdplus]

Don't you have developerAutoEnterWorld for a reason?

[IntegratedQuantum]

Right, I guess I could use that as well, still, apart from being more precise, it wouldn't actually be much different from using my phone.

[archbirdplus]

Good to know performance is in good hands. I could get time within ±0.1s out of 8.9 (lods=3).