Comment by f311a
7 hours ago
I hope they will put more resources into fixing issues. I remember there were multiple attempts to add it to ClickBench, but each time new bugs were found.
It should not be X times slower than SQLite.
7 hours ago
I hope they will put more resources into fixing issues. I remember there were multiple attempts to add it to ClickBench, but each time new bugs were found.
It should not be X times slower than SQLite.
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?
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...
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.
1 reply →
Also hilarious that the rebuttal comment after a year had passed was "why are you using this release which is a year old"
That rebuttal comment was posted in response to a comment that was 4 days old, not a year old.
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.
> Add Turso (it is unbelievably slow) (it also does not work)
Ah Alexey, never change
Another PR:
> Turso - it is ridiculously slow, can't believe that: revert the single-transaction import, cap per-query wall-clock