Lemmy

12568 readers

1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

Lemmy hardware / VPS requirements? (beehaw.org)

submitted 1 year ago by molo@beehaw.org to c/lemmy@lemmy.ml

8 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] andrew@radiation.party 8 points 1 year ago* (last edited 1 year ago) (1 children)

It sounds like Lemmy may have difficulty being scaled that hard, that quick. There are some database-side performance bottlenecks (that are being worked on actively) that block high concurrency and activity, as well as limitations in how websockets are being used in the current version that can cause dropouts on very active instances.

Both of those issues are being worked on, and it sounds like the websocket issue is particularly close to being ready for release-candidate. It really sounds like the focus on the dev's side is to prep for a possible reddit exodus before the blackout that many subs there are doing- meaning, get the software running reliably and performantly, knock out any low-hanging fruit, etc.

[–] molo@beehaw.org 3 points 1 year ago

Glad that known issues are being addressed. Ideally I wouldn't be treading new ground but rather deploying existing known patterns and best practices. But it seems like this would be a departure from existing installations. Thanks for your input.