Post AbNDaHHCltfxuHZXkW by dottorblaster@fosstodon.org
(DIR) More posts by dottorblaster@fosstodon.org
(DIR) Post #AbMlAaLYRuZUo2ZEnY by louis@emacs.ch
2023-11-01T15:02:38Z
1 likes, 0 repeats
Just gave SurrealDB 1.0.0, one of the new Rust kids on the block, a try. Goal: compare performance to PostgreSQL.Both databases were setup on the same machine (x86_64, 8 cores).Data: a table with 50.000 small rows (~60bytes). One column is a INT value between NULL and 250.The raw file size on both databases was below 9 MBs.Query in Postgres:select count(*) from objects where score > 100;Query in SurrealDB:select count() from objects where score > 100group allThe count result will be 22.000.Here are the results after a few repeated executions:No index:Postgres: 28msSurrealDB: 801msWith index:Postgres: 12msSurrealDB: 620msTime for creating the index:Postgres: 50msSurrealDB: 8.140msI'm kind of disappointed about the result, given the small table size. I can't see how SurrealDB would scale with bigger setups and wonder about the hype around it.#surrealdb #postgresql #benchmark
(DIR) Post #AbMlbLGGdz5hq3qwNs by offset___cyan@emacs.ch
2023-11-01T15:07:29Z
0 likes, 0 repeats
@louis postgres will definitely outlive all the postgres killers, except it's twin flame mariadb
(DIR) Post #AbMmM1DqxwixIcysPQ by louis@emacs.ch
2023-11-01T15:15:19Z
0 likes, 0 repeats
@offset___cyan The MariaDB Corp dug their own grave by investing all their money and resources for their cloud service "SkySQL", which they now abandoned due to cash shortage including the customers who use it. Not good.For the last two years they basically ignored serious bug reports, chasing off users to MySQL and PostgresQL. I filed two bug reports about their JSON_TABLE function which were confirmed but never fixed, making it virtually unusable.Big drama between MariaDB Corp and MariaDB Foundation. I can't take them serious anymore.
(DIR) Post #AbMmVQnpEEuHF1IKv2 by offset___cyan@emacs.ch
2023-11-01T15:17:39Z
0 likes, 0 repeats
@louis I didn't realise, I'll have to look into that. Sounds completely discouraging and all the more reason for me to pick Postgres next time I start a db-intensive project (I use SQLite at the moment, usually)
(DIR) Post #AbMs9kL6VhZnBgu5dw by louis@emacs.ch
2023-11-01T16:20:56Z
0 likes, 0 repeats
@offset___cyan SQLite never disappoints and it would be my first choice if I did not need remote access to the database from different clients.
(DIR) Post #AbMwUcmSD0TZdruJeK by offset___cyan@emacs.ch
2023-11-01T17:09:32Z
0 likes, 0 repeats
@louis have you thought about experimenting with that LibSQL distributed DB you shared the other day?
(DIR) Post #AbN13hNTVZzZqsCgu8 by louis@emacs.ch
2023-11-01T18:00:42Z
0 likes, 0 repeats
@offset___cyan I had a great chat with Glauber Costa, one of the founders of Turso, the other day and I still experiment with it. However, when you work with remote SQLite, your tooling must explicitly support/implement libSQL. They have libs for programming languages but there is no GUI that supports it as of today.So you can't just pop up your client and look into the database or export/import some data. For that you either have to write scripts in a supported programming language or download the whole database to your local machine. When you deal with databases > 10 or even 100 GB, it quickly becomes an issue.Same goes for backups. There is no backup service that supports it (yet), so you have to roll your own solution and copy (meaning: download) the whole database to some external machine every day (or multiple times a day).While Turso has great features like replication to multiple regional zones etc. it is designed so that you have many little databases per tenant or user.My use case is more traditional in that I often need to work on the live database, which is currently 150 GB and growing.
(DIR) Post #AbNDaHHCltfxuHZXkW by dottorblaster@fosstodon.org
2023-11-01T20:21:02Z
0 likes, 0 repeats
@louis @xgqt woh. To be honest I expected so much more, this is very meh. I hope future releases get better, but I have to say Postgres never disapponted me and I never actively looked for a replacement in my use cases