Comment by menaerus
6 hours ago
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.
> 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...
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.