5 ms·

Insane! $110M towards yet another Postgres extension. Theoretical CS and hardware has advanced so much, but the people are using the same old boring approaches.

Insane! $110M towards yet another Postgres extension. Theoretical CS and hardware has advanced so much, but the people are using the same old boring approaches. Truly sad.

Beltalowda 5y ago
What do you think better alternatives/approaches are?
- dboreham 5y ago
  PostgresSQL process-per-connection execution model is limiting.
- ashvardanian 5y ago
  Literally anything. There is so much to do better. Faster I/O, kernel bypass and async filesystem, new persistent data-structures, alternative lock-free concurrency resolution schemes… Disclaimer: I am highly biased, as I am funding/researching/developing a DBMS myself. Out of necessity though, as we constantly hit bottlenecks in the persistent I/O layer. We are not selling or offering anything, but will soon share some fresh internal results on aforementioned topics. In the meantime, here is a list of startups re-implementing mostly identical ideas: https://unum.cloud/post/2021-12-31-dbms-startups/ https://unum.cloud/post/2021-12-31-dbms-startups/
pella 5y ago
"boring" == less transactional surprise :-) https://jepsen.io/analyses/postgresql-12.3 https://jepsen.io/analyses/postgresql-12.3
pella 5y ago
proposal for "Solving PostgreSQL wicked problems" https://github.com/orioledb/orioledb/blob/main/orioledb-postgresbuild-2021.pdf https://github.com/orioledb/orioledb/blob/main/orioledb-post...
- ashvardanian 5y ago
  Great report, but I am new B-Trees alone will not enough. The simplest common solution is to switch to LSM Trees for higher write throughput. Thats exactly what Yugabute does, by putting Postgres over RocksDB. Same way as Facebook uses MyRocks = MySQL + RocksDB.
- rektide 5y ago
  Nice share. Oriole DB updated the readme 17 days ago to say they'd release in February 2022, so I'll definitely be watching this space. These sounds like some really interesting striking-at-the-heart-of-it changes. I hope we have a long time to see which of these pan out & pay off big. On a side note, nice interesting brief comments & shares elsewhere on this site. :thumbup:
_joel 5y ago
True, why use proven technology with decades of production usage with your data when you can use a novel and theoretical CS paper implementations.

Insane! $110M towards yet another Postgres extension. Theoretical CS and hardware has advanced so much, but the people are using the same old boring approaches. Truly sad.

Beltalowda 5y ago

What do you think better alternatives/approaches are?

dboreham 5y ago
PostgresSQL process-per-connection execution model is limiting.
ashvardanian 5y ago
Literally anything. There is so much to do better. Faster I/O, kernel bypass and async filesystem, new persistent data-structures, alternative lock-free concurrency resolution schemes… Disclaimer: I am highly biased, as I am funding/researching/developing a DBMS myself. Out of necessity though, as we constantly hit bottlenecks in the persistent I/O layer. We are not selling or offering anything, but will soon share some fresh internal results on aforementioned topics. In the meantime, here is a list of startups re-implementing mostly identical ideas: https://unum.cloud/post/2021-12-31-dbms-startups/ https://unum.cloud/post/2021-12-31-dbms-startups/

pella 5y ago

"boring" == less transactional surprise :-) https://jepsen.io/analyses/postgresql-12.3 https://jepsen.io/analyses/postgresql-12.3

pella 5y ago

proposal for "Solving PostgreSQL wicked problems" https://github.com/orioledb/orioledb/blob/main/orioledb-postgresbuild-2021.pdf https://github.com/orioledb/orioledb/blob/main/orioledb-post...

ashvardanian 5y ago
Great report, but I am new B-Trees alone will not enough. The simplest common solution is to switch to LSM Trees for higher write throughput. Thats exactly what Yugabute does, by putting Postgres over RocksDB. Same way as Facebook uses MyRocks = MySQL + RocksDB.
rektide 5y ago
Nice share. Oriole DB updated the readme 17 days ago to say they'd release in February 2022, so I'll definitely be watching this space. These sounds like some really interesting striking-at-the-heart-of-it changes. I hope we have a long time to see which of these pan out & pay off big. On a side note, nice interesting brief comments & shares elsewhere on this site. :thumbup:

_joel 5y ago

True, why use proven technology with decades of production usage with your data when you can use a novel and theoretical CS paper implementations.