I’m wondering for future performance/optimization goals, if it’s possible to examine the VM code that is generated by LuaJIT in some way so I can understand the implications of certain code changes to my game. I know the memory requirements are likely to be fairly high (~1 GB, hopefully less than 2 GB maximum) by the time my game is complete due to the amount of action taking place. However, I want to make sure it will perform on mid-range devices and I’m not a huge fan of profiling as it usually doesn’t direct the developer to the exact problem situation. I’d rather just diff the VM assembly directly for a few test cases and then make some decisions with that information so going forward I use the proper logical style to handle certain familiar situations.
The files are called .luac after compilation. They’re wrapped in our format, but you can probably dig it out from there.
1 Like