Niklas Frykholm wrote: > It seems like the JIT FFI path hits some pathological case that leads to > very bad performance. Any idea what this might be? This is unlikely, because this example is so simple. Check the output of -jv or the equivalent: require("jit.v").start("output.txt") Maybe the JIT compiler has trouble allocating executable memory on Android? There was a report of this happening with a Tegra chipset, where the whole virtual memory address range was polluted with tiny blobs. OTOH ... how did you test? An individual test run for each case or a shared test loop? --Mike