Is Memory64 actually worth using?

The Memory64 proposal for WebAssembly adds 64-bit pointers, now supported in Firefox 134 and Chrome 133. While 64-bit WebAssembly allows for addressing more memory, it tends to run slower than 32-bit due to necessary bounds checks and hardware constraints. This performance penalty can range from 10% to over 100%. Memory64 might be useful for applications needing more than 4GB of memory but comes at the cost of slower performance. Future optimizations and hardware improvements may reduce this penalty.