postgres-benchmarks
neon-vercel-zapatos
postgres-benchmarks | neon-vercel-zapatos | |
---|---|---|
4 | 1 | |
69 | 1 | |
- | - | |
10.0 | 3.8 | |
over 3 years ago | 9 months ago | |
JavaScript | TypeScript | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postgres-benchmarks
-
PostgresJs: The Fastest full featured PostgreSQL client for Node.js and Deno
There's a link to a simple Benchmark right after the title.
Here are two:
https://github.com/porsager/postgres-benchmarks
https://porsager.github.io/imdbench/sql.html
-
Does Prisma work in production?
and really fast (https://github.com/porsager/postgres-benchmarks) even faster than the native postgres
-
Show HN: Postgres.js – Fastest Full-Featured PostgreSQL Client for Node and Deno
> On the surface I'm not sure this explanation passes the smell test. Almost irrespective of how you get the data from your network card into v8 / nodejs, you're going to be crossing c++/v8 boundaries.
yes, you are, but the differences are the object creation that occurs. a single buffer coming from c/c++ (a socket, let's say) can be parsed and turned into a large number of objects in javascript much more quickly. yes, you're passing through that barrier once, but creating all of those objects from c++ and passing through it 20-30 times is a lot more expensive.
> Out of curiosity, do you have links to these other projects where they have similar benchmarking attempts/results?
how about pg vs pg-native? https://github.com/porsager/postgres-benchmarks#results
and unfortunately, I cannot find the original discussions from when node-redis went from native to pure javascript, but it was about a 30-40% speed increase originally if memory serves (I was the one who did that original conversion after a lot of deep dives into v8 and performance crossing the barrier).
as an aside, I'm also the maintainer of plv8, and am happy to discuss the same types of performance issues of dealing with jsonb vs json (which in Postgres is text): creating objects vs a simple JSON.parse() in c++ is a significant difference.
neon-vercel-zapatos
-
PostgresJs: The Fastest full featured PostgreSQL client for Node.js and Deno
It should be, now that pg runs fine there. If it’s not, please file an issue!
It also works with @neondatabase/serverless on platforms without TCP connections (though it’s on my TODO list to make this less fiddly): https://github.com/neondatabase/neon-vercel-zapatos
What are some alternatives?
plv8 - V8 Engine Javascript Procedural Language add-on for PostgreSQL
pitwall-pg - A postgres library to help write safe, parameterized, transaction-aware SQL for when an ORM or query builder isn't the right tool for the job
prisma-redis-middleware - Prisma Middleware for caching queries in Redis
postgres - Postgres.js - The Fastest full featured PostgreSQL client for Node.js, Deno, Bun and CloudFlare
serverless - Connect to Neon PostgreSQL from serverless/worker/edge functions
pgtyped - pgTyped - Typesafe SQL in TypeScript
mammoth - A type-safe Postgres query builder for TypeScript.
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
postgres-shift - A simple forwards only migration solution for postgres.js
node-redis - Redis Node.js client
StrikeDB - Promisified server-side prepared statements for node mysqljs