|
|
|
|
|
|
by RedCrowbar
1590 days ago
|
|
|
We've got some benchmarks in an earlier blog post [1]. EdgeDB is designed to do its job validating and compiling your schema and queries and then get out of the way. In other words, once a query was first parsed and compiled, the cost of the next trip via EdgeDB would be similar to that of pgbouncer, i.e. we'll simply send the compiled SQL to Postgres and proxy the results back to the client. This is why our data protocol uses Postgres framing and encoding. [1] https://www.edgedb.com/blog/edgedb-1-0-alpha-1 |
|
|