Bug: Benchmarks unreliable as they run in the same process.

[samal-rasmussen]

I initially filed a bug for better-sqlite3 after seeing these benchmarks, and JoshuaWise was kind enough to spend time looking into it. His response here:
WiseLibs/better-sqlite3#1008 (comment)

So this is a bug report for these benchmarks reporting that they are unreliable, as they are not run in separate processes. Detailed description in JoshuaWise's comment.

[AndriiSherman]

@samal-rasmussen, thanks a lot!
We have this repo open for specific purposes, so anyone can help us find any mistakes made in this benchmark repo.
We will analyze your feedback and the entire thread you've sent and improve this repo accordingly.

Furthermore, if you have any suggestions or changes to the code, please feel free to submit a PR with the modifications. We would love to learn from it and present accurate data to everyone.

[samal-rasmussen]

It looks like you already have benchmark scripts that only test one library at a time. E.g:
https://github.com/drizzle-team/drizzle-northwind-benchmarks/blob/master/src/drizzle/benchmark.ts
https://github.com/drizzle-team/drizzle-northwind-benchmarks/blob/master/src/better-sqlite3/benchmark.ts

So you just need to remove the benchmark script that runs multiple libraries in the same process:
https://github.com/drizzle-team/drizzle-northwind-benchmarks/blob/master/src/common/benchmark.ts