6 ms·
> Comparing those numbers with a similar api built using fastapi and asyncpg, there was if i remember correctly at least 4x to 5x throughput increase. I wonder
by returningfory2 3y ago
> Comparing those numbers with a similar api built using fastapi and asyncpg, there was if i remember correctly at least 4x to 5x throughput increase.
I wonder to what extent this improvement comes from not using Python, as opposed to using this alternative solution? For example after Python to Go migrations it’s common to see this kind of speed up I believe.
- fulafel 3y agoThey might have used Python still - the Omnigres page lists Python support, and PG has had PL/Python for a long time.
- yrashk 3y agoWe are working on first-class support for Python indeed (and other languages like JavaScript) An important thing here is that we see Omnigres as a polyglot runtime with a database inside (Postgres) and we want people to use languages they prefer.
- yrashk 3y agoIn my tests, I was testing against Node.js and Rust and was getting roughly the same numbers. https://yrashk.com/blog/2023/02/16/what-happens-if-you-put-http-server-inside-postgres/ https://yrashk.com/blog/2023/02/16/what-happens-if-you-put-h... In the instance of short-living queries, we are able to get this by effectively removing the communication latency.