• Imaginos@lemmy.world
      link
      fedilink
      English
      arrow-up
      16
      ·
      1 year ago

      Looks like the app wasn’t developed with a scalable architecture from the start, then they strapped some caching out of desperation when users started flocking, and didn’t consider the invalidation parameters for private pages correctly.

      • StateMachine@lemmy.world
        link
        fedilink
        Interlingua
        arrow-up
        1
        ·
        1 year ago

        It’s a little bit baffling. It’s not like they couldn’t have predicted this server load. I know it’s tricky to foresee bottlenecks in some situations but them adding caching (a very basic thing for scalability) at the last minute belies a lack of either experience, forethought, or knowledge, I am not sure which.

    • meisterlix@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Did you report this (on GitHub possibly)? That seems to be a fairly important bug for the devs to get their head around.

    • Troy
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I’ve seen the same thing when using the web interface. It’s very brief – like a flicker or something.