News for hackers. Stuff that matters.
Re:Supabase Is Acquiring Turso by f311a on Friday October 02, 2026 @12:16PM (#49935239)
I hope they will put more resources into fixing issues. I remember there were multiple attempts to add to ClickBench, but each time new bugs were found.

It should not be X times slower than SQLite.

https://github.com/ClickHouse/ClickBench/issues/336

Re:Supabase Is Acquiring Turso by menaerus on Friday October 02, 2026 @12:47PM (#49935677)
On 22nd of July

> It was loading the data for a week already, and the speed of loading data has dropped to 4 kilobytes per second, and it will take years to load the dataset.

And then on 2nd of August

> It loaded maybe 1% of the data so far.

And then one year after

> I didn't load the data after a year. > I tried it with the fsync removed, but even then it does not work

Ok, I find this more entertaining than I should and almost unbelievable. I know that this codebase was heavily written by LLMs but the execution can't be this bad?

What am I missing and why would Supabase buy the product which can't even load the dataset properly?

Re:Supabase Is Acquiring Turso by gpm on Friday October 02, 2026 @01:06PM (#49935894)
You're looking at a software project months after its inception, saying it didn't work well then, and then asking why someone would buy it well over a year later...
Re:Supabase Is Acquiring Turso by menaerus on Friday October 02, 2026 @01:15PM (#49936001)
1st commit of the project was in August 2023 so not quite few months old. And the performance problem according to https://github.com/ClickHouse/ClickBench/pull/1159 has not been yet solved.

So, I think my curiosity still stands.

Re:Supabase Is Acquiring Turso by gpm on Friday October 02, 2026 @01:24PM (#49936114)
> 1st commit of the project was in August 2023

Yeah, ok, I took the date from [1] but you're right the project did in some sense exist before then.

[1] https://turso.tech/blog/we-will-rewrite-sqlite-and-we-are-go...

Re:Supabase Is Acquiring Turso by ambicapter on Friday October 02, 2026 @12:57PM (#49935805)
Also hilarious that the rebuttal comment after a year had passed was "why are you using this release which is a year old"
Re:Supabase Is Acquiring Turso by gpm on Friday October 02, 2026 @01:05PM (#49935886)
That rebuttal comment was posted in response to a comment that was 4 days old, not a year old.
Re:Supabase Is Acquiring Turso by dangoodmanUT on Friday October 02, 2026 @01:45PM (#49936340)
> Add Turso (it is unbelievably slow) (it also does not work)

Ah Alexey, never change

Re:Supabase Is Acquiring Turso by f311a on Friday October 02, 2026 @02:03PM (#49936599)
Another PR:

> Turso - it is ridiculously slow, can't believe that: revert the single-transaction import, cap per-query wall-clock

Re:Supabase Is Acquiring Turso by penberg on Friday October 02, 2026 @02:07PM (#49936640)
We're aware of your woes with ClickBench. The first time you added it I even explicitly told you that it was way too early to even try that. The attempt you did recently was fair, but it's all in the ingestion before the benchmark, and does not show up anywhere, so we ended up spending time on this instead:

https://turso.tech/blog/turso-0.8.0

In any case, this is on our radar and we do intend to improve it but not the highest priority right now.

Re:Supabase Is Acquiring Turso by rendaw on Saturday October 03, 2026 @12:55PM (#49945872)
Why do you think f311a is alexey?
Re:Supabase Is Acquiring Turso by hitekker on Saturday October 03, 2026 @07:28PM (#49948816)
I also want to know that; it's a weird accusation.

Penberg's earlier reply said f311a was (paraphrased) "talking crap on the internet" but it looks like they've edited out the cussing.

Re:Supabase Is Acquiring Turso by f311a on Sunday October 04, 2026 @11:19AM (#49954644)
I'm not affiliated in any way.
Re:Supabase Is Acquiring Turso by egorfine on Saturday October 03, 2026 @08:12AM (#49943593)
I hope they don't. Of the many projects in the world, SQLite is one of the very top in the list of "do not rewrite".