5 ms·
> LuaJIT doesn’t always magically fix that. Not to mention there are some significant performance issues on aarch64. Love2D, a popular game framework, opted to
by Yliaho 2y ago
> LuaJIT doesn’t always magically fix that.
Not to mention there are some significant performance issues on aarch64. Love2D, a popular game framework, opted to not use JIT on macOS for this reason.
https://github.com/LuaJIT/LuaJIT/issues/285 https://github.com/LuaJIT/LuaJIT/issues/285
- aeadio 2y agoThis is strictly about how much memory LuaJIT can address on that platform. There’s no “significant performance issues”. If your workload fits inside 2 GiB (IIRC) it will be fast. LuaJIT is a world class JIT. For a long time a new garbage collector has been an open issue for LuaJIT, which would fix this particular issue, and make the language even faster. Last I checked this was actively being worked on.
- epcoa 2y ago> This is strictly about how much memory LuaJIT can address on that platform No it is not. https://github.com/LuaJIT/LuaJIT/issues/285#issuecomment-1971854441 https://github.com/LuaJIT/LuaJIT/issues/285#issuecomment-197... > If your workload fits inside 2 GiB (IIRC) it will be fast. This has nothing to do with the issue being mentioned here. You are understating the severity of this issue and seem to be confusing it with a different issue that is no longer relevant in 2.1.