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.
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?
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.
Thanks, appreciate the data point.
Can you provide any info about the number of pageviews/month or pageviews/hr that setup can support for lemmy?