On Thursday 20 September 2007 11:20:45 François PERRAD wrote: > >Umm, before I make a fool of myself over there ... I've tested > >this with a few benchmarks. So, maybe I'm missing something > >essential, but why does --jit-core *slow down* things (5%-10% > >slower than --computed-goto-core)?
JIT's much better for long-running processes. The last time I profiled a test with JIT, the process spent most of its time *generating* the JIT code. The result ran faster than even the CGP code, but the process didn't run the JITted code long enough to overcome the cost of JITting. > >And even if it's only interpreted, 20x-33x *slower* than the Lua > >interpreter seems a bit hefty. And comparing (supposedly) JIT > >compilers, it's 50x-200x slower than LuaJIT 1.1. > >Do I need to disable some debug stuff? I just followed the > >standard build instructions ... Parrot has some known (unenabled) optimizations, and we haven't really focused on optimizations much yet, as we're still adding features. I have a couple of Parrot Lua failures that I hope François can resolve, but I'm happy to do some optimization work where appropriate. -- c
