‹ BackHN Continuity

Thread

Supabase is acquiring Turso

218 points · 117 comments · cvburgess

  1. f311a · · focus · HN ↗
    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.

    <a href="https:&#x2F;&#x2F;github.com&#x2F;ClickHouse&#x2F;ClickBench&#x2F;issues&#x2F;336" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ClickHouse&#x2F;ClickBench&#x2F;issues&#x2F;336

    <a href="https:&#x2F;&#x2F;github.com&#x2F;ClickHouse&#x2F;ClickBench&#x2F;pull&#x2F;1009" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ClickHouse&#x2F;ClickBench&#x2F;pull&#x2F;1009

    1. menaerus · · focus · HN ↗
      On 22nd of July

      &gt; 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

      &gt; It loaded maybe 1% of the data so far.

      And then one year after

      &gt; I didn&#x27;t load the data after a year. &gt; 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&#x27;t be this bad?

      What am I missing and why would Supabase buy the product which can&#x27;t even load the dataset properly?

      1. ambicapter · · focus · HN ↗
        Also hilarious that the rebuttal comment after a year had passed was &quot;why are you using this release which is a year old&quot;
        1. gpm · · focus · HN ↗
          That rebuttal comment was posted in response to a comment that was 4 days old, not a year old.
      2. gpm · · focus · HN ↗
        You&#x27;re looking at a software project months after its inception, saying it didn&#x27;t work well then, and then asking why someone would buy it well over a year later...
        1. menaerus · · focus · HN ↗
          1st commit of the project was in August 2023 so not quite few months old. And the performance problem according to <a href="https:&#x2F;&#x2F;github.com&#x2F;ClickHouse&#x2F;ClickBench&#x2F;pull&#x2F;1159" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ClickHouse&#x2F;ClickBench&#x2F;pull&#x2F;1159 has not been yet solved.

          So, I think my curiosity still stands.

          1. gpm · · focus · HN ↗
            &gt; 1st commit of the project was in August 2023

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

            [1] <a href="https:&#x2F;&#x2F;turso.tech&#x2F;blog&#x2F;we-will-rewrite-sqlite-and-we-are-going-all-in" rel="nofollow">https:&#x2F;&#x2F;turso.tech&#x2F;blog&#x2F;we-will-rewrite-sqlite-and-we-are-go...

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.