EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Aug 6·5 min read
The LuaJIT NYI That Silently Poisoned an Unrelated Hot Loop
TL;DR
A performance issue in LuaJIT, the just-in-time compiler for Lua, can drastically affect execution speed due to 'Not Yet Implemented' (NYI) operations. A specific NYI caused a 20× difference in iteration counts during benchmarking.
✦ Why It Matters
Review your LuaJIT code for potential NYI operations to avoid performance degradation.
Key Takeaways
- Avoid using 'unpack' in hot loops to prevent performance degradation.
- Implement specialized wrapper functions to maintain JIT compilation.
- Monitor LuaJIT trace output in CI to catch NYIs early.
- Move nested functions outside of loops to optimize performance.
How It Works
LuaJIT uses a tracing JIT compilation approach, recording execution paths to optimize performance. However, certain operations like 'unpack' trigger a fallback mechanism that can lead to blacklisting functions, causing significant slowdowns.
By generating specialized wrappers that directly access function arguments, the need for 'unpack' is eliminated, allowing the JIT compiler to maintain optimized execution.