The assumption that a lot of this is memory memory allocations and copies as values are passed between the C, Rust, and JavaScirpt layers. We also suspect that Neon Bindings may be less efficient than better-sqlite3 is which seems to hook into the V8 APIs directly.
Let's improve the benchmarks, profile, and fix performance to be on-par with better-sqlite3.
This would be great; think there is most every feature I want here in replacing and improving on better-sqlite3 (once extension support in 0.40 lands), except performance.
We are still a bit behind
better-sqlite3
. For example, there's more overhead inget()
:The assumption that a lot of this is memory memory allocations and copies as values are passed between the C, Rust, and JavaScirpt layers. We also suspect that Neon Bindings may be less efficient than
better-sqlite3
is which seems to hook into the V8 APIs directly.Let's improve the benchmarks, profile, and fix performance to be on-par with
better-sqlite3
.