Selfhosted

38768 readers

368 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

What specs for a self-hosted Lemmy instance? (aussie.zone)

submitted 1 year ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

Hi all, a shout-out for assistance. I’m considering hosting a Lemmy instance (assuming I can pass the wife test on costs) and I’m looking for some guidance on specs.

Can anyone who’s currently hosting an instance (or who knows the inner workings of one) please reply with:

specs on the hardware / VPS that’s hosting your instance
how many users / posts that’s supporting
what the system load looks like with the above
if locally hosting, the type of bandwidth requirements you’re seeing

I previously posted this in the wrong community, and one of the responses asked how many users I'm expecting. To preemptively answer - I don't know. I'm just trying to get an idea of relative sizing.

Thank you!!

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

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

It's pretty lightweight. I've given each container 1/3Gi of memory and 1CPU limit with low requests. Utilizing kubernetes HPA to scale containers under load up to 4 replicas. It only scales when a user takes large actions (subscribing to hundreds of new to the instance communities at once). But once the initial federation begins it seems to quickly scale back down. The biggest bottleneck is pictrs since it is stateful.

So far the database and pictrs is only about 2Gi of storage but I've allocated 25Gi to each since I have a lot to spare at the moment.

I have to play with the HPA more since I'm not happy yet with my settings. I have 2 users and 1 bot on my instance.

I'd like to start contributing to Lemmy's codebase so I wanted to host my own instance to learn the inner workings.

My postgres is a single replica at the moment but I may scale that if stability is becomes a problem.