Details here: https://github.com/LemmyNet/lemmy/issues/3165

This will VASTLY decrease the server load of I/O for PostgreSQL, as this mistaken code is doing writes of ~1700 rows (each known Lemmy instance in the database) on every single comment & post creation. This creates record-locking issues given it is writes, which are harsh on the system. Once this is fixed, some site operators will be able to downgrade their hardware! ;)

  • BeigeAgenda
    link
    fedilink
    arrow-up
    15
    ·
    1 year ago

    Get some DBA’s on the job and Lemmy will be blazing fast.

    • RoundSparrow@lemmy.mlOPM
      link
      fedilink
      arrow-up
      14
      ·
      1 year ago

      We have had DBA’s, the problem is the Rust code uses ORM and an auto JSON framework that makes tracing the code time-consuming to learn.

      • BeigeAgenda
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Okay so you may need to refactor here and there to get more performance.

        • RoundSparrow@lemmy.mlOPM
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          In this one case, it was hand-written SQL inside a PostgreSQL FUNCTION that the ORM knows nothing about. But there is a approach in the entire application to have live-data from PostgreSQL for every little thing.