this post was submitted on 20 Jun 2023
45 points (97.9% liked)

Selfhosted

40358 readers
381 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Are there any Discord servers or somewhere in the Matrix to chat about hosting a Lemmy instance? I've got Lemmy running, but I think there are several of us in the same boat struggling with federation performance issues and it might be good to have some place to chat real time.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

They've bumped the server much more than the original posted VM. I was pointing to the zabbix charts and actual usage. Notice CPU is sub 20%, and the network usage being sub 200Mbits. There's plenty of headroom.

[–] [email protected] 1 points 1 year ago (1 children)

I found the newest link- https://lemmy.world/comment/379405

Ok, that is a pretty sizable chunk of hardware.

[–] [email protected] 1 points 1 year ago (1 children)

I care less about what it is running on, but what is consumed. At sub 20% usage, it really doesn't matter what the hardware is, because the overall spec is not the bottle neck.

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

Your original link is from 9 days ago, before the massive surge hit.

https://lemmy.world/post/56228 Came 8 days ago, with reports of it being pretty well saturated.

Remember- the big surge, is in the last 3-4 days.

Fediverse stats: https://fediverse.observer/dailystats

In the last 4 days, they have went up over 400% in size.

[–] [email protected] 1 points 1 year ago (1 children)

I don't know if you're totally missing it... here is the CPU usage from 3 hours ago: https://lemmy.world/comment/377946

Even if you 4x the usage from the alleged 400% growth, the spec of the server itself is not the bottleneck. They've also significantly increased the federation workers to 10000 based on my private chat... so something is not scaling to the fullest potential.

I think the point of focus should be more on why it is not using all the resources available, rather than 'that server is weak'. We're about to see a much larger influx up comes July 1st that's going to make the 400% growth look like a joke, and if current larger instances aren't able to handle the federation now, the current smaller instances will buck hard up comes the big move.

[–] [email protected] 1 points 1 year ago (1 children)

Ok- sorry- I 100% missed that.

I am onboard with you now.

Hopefully the upcoming 0.18 release I keep hearing about helps compensate for a few of these issues...

[–] [email protected] 1 points 1 year ago (2 children)

Quick skim through the commits on the master branch, I don't see many changes pertaining to federation. This one looks interesting/related, but I think in itself only tells server admins when to increase worker counts: https://github.com/LemmyNet/lemmy/commit/25275b79eed0fb1fe90d27c197725f510f9965bb

[–] [email protected] 2 points 1 year ago (1 children)

Don't know if they changed it or not-

But, I am busy making a few kubernetes manifests for deploying lemmy- and I am noticing a ton of extra debugging / logging that doesn't need to be there for production use.

Seriously doubt it's going to fix the issue- but, reducing some of the debugging enabled by default, wouldn't hurt.

[–] [email protected] 1 points 1 year ago (1 children)

100% with you. A lot of the current deployment are very development centric... Let's pretend the default docker-compose.yml isn't opening up the postgres DB to the internet with a generic password...

The pace the entire system must mature to enable the platform to handle the hopeful upcoming growth is... interesting, to say the least...

[–] [email protected] 1 points 1 year ago

Well, if I can knock out a decent helm chart for these manifests, it might actually help a bit-

Most of the components can scale quite easily on k8s. The only piece I am unsure of currently, is lemmy itself.

The lemmy-ui scales. Appears mostly stateless. pictrs scales. postgres scales.