Hello, all. I’m considering creating a Lemmy instance in order to facilitate migration of a moderately sized reddit community to the fediverse.

The community is about 150k users with around 1.5M pageviews per month.

I don’t expect everyone to come with the migration, but I would expect a significant portion to do so. Perhaps half.

How do I go about capacity planning / sizing for such an instance? Is Lemmy designed to operate at this scale?

Thanks for your input.

  • poVoq@slrpnk.net
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    Lots of unknowns right now. The best might be to look for a VPS provider that allows scaling up relatively easily.

    Besides some low hanging fruits that are being worked on right now, it is simply unknown as no Lemmy instance has so far operated at this scale. The techstack (rust and postgres) is relatively performant though. Main bottleneck is likely going to be the database for now.

    • molo@beehaw.orgOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Thanks, appreciate your input.

      If postgres is the scaling limit on most deployments, I assume normal postgres scaling via replicas and sharding would apply.

      Is the frontend amenable to heavy caching for non-logged-in views?

      • poVoq@slrpnk.net
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        Yes horizontal scaling of Postgres probably works especially together with running multiple Lemmy backends behind a load balancer. But I am not aware of anyone running such a setup right now.

        Caching is being worked on right now and should be available together with the no-websockets improvement very soon.