Node.js 26.9 turns node:ffi on by default at 37 nanoseconds a call

8.8 relevance

Deep performance analysis of Node.js FFI, highly actionable and technical.

AI/ML dev.to

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For a platform engineer managing containerized Node deployments, removing the node-gyp toolchain simplifies CI/CD and reduces image size, but the 37ns overhead and experimental status require careful workload selection—bulk data operations benefit, while high-frequency small calls do not.

Key Takeaways

Benchmark your native call patterns: use node:ffi for bulk buffer operations, but stick with N-API or plain JS for high-frequency small calls.

Node.js 26.9 turns node:ffi on by default at 37 nanoseconds a call

Summary

Node.js 26.9.0 enables node:ffi by default, allowing C function calls at ~37ns per invocation—7-8% slower than N-API addons but 15-20% faster for bulk buffer operations like summing 10M floats. The change eliminates node-gyp dependencies and the experimental flag, though the module remains experimental and unsafe (wrong signatures crash the process). This shifts the tradeoff: FFI wins on convenience and data-heavy workloads, not per-call performance.

Author

Alex Georgiev