Hello friends!

Lemmy.ca will be undergoing scheduled maintenance from approximately 12:00 - 12:30 PT (3:00 - 3:30 ET), while we move to a more powerful server.

Happy Canada day!

  • Shadow@lemmy.caOPM
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Disk, due to low memory. Not enough to keep enough of the db in memory, and having to hit disk for pictures as well.

    • lightrush@lemmy.ca
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Oh I see. Makes sense. Do you know if the storage was NVMe previously or spinning media?

      • Shadow@lemmy.caOPM
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        It was a VPS and I think on some sort of shared SATA/SAS SSD array, just going off the 300-800MB/s reads I was seeing.

        Old box: Timing buffered disk reads: 2066 MB in 3.00 seconds = 687.62 MB/sec

        New box: Timing buffered disk reads: 1022 MB in 0.31 seconds = 3338.77 MB/sec

        • lightrush@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Nice uplift. Random IO which is likely what the db does are probably through the roof compared to the sequential uplift.

          • Shadow@lemmy.caOPM
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            The DB is small enough it’s all in ram now, seeing a 100% cache hit rate in postgres.

            • lightrush@lemmy.ca
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              Nice. You could post any screenshots and copy-pasta if you collect them anyways from stuff you find interesting while working on the instance. I’m sure there’s a lot of technical folks around here other than us that would find it fun to look at. Only if it’s not significant additional work of course. 😁