Suggestion for even higher performance gains

[cipharius]

Suggestion for even higher performance gains

[ffrostflame]

This method is faster and better performance without native code generation, however, in native code generation, buffers outperform tables and functions.

I used to use an approach like this, and it works well w/o codegen enabled. But the second you enable codegen, things change.

I'll likely be using this approach on the client, and the resizing approach on the server.

[cipharius]

I don't see how native codegen could change the memory access and allocation patterns. I am not suggesting to use table, but to use a single buffer that is allocated once instead of reallocated multiple times.

Memory reallocation has signifficant performance implications even in compiled C/C++/Rust whichever code.

[ffrostflame]

Because using purely buffers is faster than using tables alongside buffers. That's all.

Tables also need to allocate their own memory. I'll leave this open because it's actually accurate: this is the better method when considering the overhead of creating buffers, but there is no overhead for that in native codegen.