2 ms·

Oh wow, this is great. Congratulations Yurii. So i Tried omnigress to build a simple api that does few db calls a month back to mock real world scenario. And d

Oh wow, this is great. Congratulations Yurii. So i Tried omnigress to build a simple api that does few db calls a month back to mock real world scenario. And damn, the numbers were quite thought provoking. 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. Even though the project is in quite nascent stage, the idea is promising. This tackles the concept or should i rephrase, pain of having multiple platform to run a service and the needed expertise that is necessary. If the scaling part and dev convenience can be fully sorted, and also the security aspect like many have highlighted, this could very well have the potential to change the game.

vira28 3y ago
Those numbers sound similar to what the author benchmarked in the past. 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...
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 ago
  They might have used Python still - the Omnigres page lists Python support, and PG has had PL/Python for a long time.
  - yrashk 3y ago
    We 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 ago
  In 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.

vira28 3y ago

Those numbers sound similar to what the author benchmarked in the past. 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...

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 ago
They might have used Python still - the Omnigres page lists Python support, and PG has had PL/Python for a long time.
- yrashk 3y ago
  We 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 ago
In 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.