I’m smoking weed about it.
- 0 Posts
- 33 Comments
4·1 month agoSubscriber Growth
!weedtime@walledgarden.xyz, weedtime, 93 => 104, 92 posts (18 this week)
🙏
I’m not sure it’s been entirely solved. Our host is working through an unrelated hardware problem that hit in the middle of our last round of tuning but things have been behaving better aside from that.
The answer for us has been in adjusting the lemmy pool size to the database and tweaking the available resources to find a happy medium.
Can my humble, single-user instance handle it?
Maybe?
FWIW this information is based on the experience when using remote hosting not self hosting.
The main issue for us was tuning the database performance. The bot can beat your database to death sometimes and just throwing resources at it won’t necessarily solve it. related low effort meme Our experience was that the bot performance hit wasn’t really noticable immediately but it adds up as more and more communities are added to the database. There also seem to be bursts of database load at times, maybe that’s when new instances join the network? They seem to only last a short time though and haven’t really caused problems.
TLDR- Expect an eventual performance hit. If it’s too much you can always disable the bot or adjust what it does.
Seems a bit more normal today, cool.
walledgarden.xyz📢
Bot seems fine to me lololololol
!gardengrooves@walledgarden.xyz topping the list with the bot on the fritz, you love to see it.
Update to this-
After talking with my host some adjustments were made that should correct the curl error. I still don’t believe this has anything to do with the lost sync but it’s one less thing to worry about. Thanks for the information and help!
I saw your comment but I was mainly concerned with getting the instance to show up on lemmyverse at the time, which I suspected was the connection being blocked by our host (it was). Coincidentally since getting listed lemmyverse has been having its own problems so I put it on the back burner.
I’ll do some deeper digging into this and see what I can figure out. I don’t think it has anything to do with the communities falling out of sync since it’s never mattered before now and WG isn’t the sole instance being impacted, but it should work correctly either way.
I’m having similar issues with a number of instances. Users have reported verified federation delays between walledgarden and several other places including lemmy.ml, hexbear.net, feddit.org, vegantheoryclub.org, and possibly others. Before anyone says it- yes I know they don’t federate with everyone but walledgarden isn’t being blocked/defedded.
Walledgarden seems to be able to retrieve the data from them, but WG communities stopped federating to them a few days to a week or more ago in many cases, and as recently as yesterday in others. I’ve been working through it with our host but so far we haven’t figured it out since there isn’t anything obvious causing the problem on our side. As far as I can tell replies and interactions from walledgarden still make it to those instances without issue.
It’s very frustrating.
Lemmy seems to be on the fritz lately. I’ve noticed lots of weird federation/sync issues, with even the big places like .world having problems recently. Very strange behavior across the board the last couple weeks.
11·2 months agoPrivate in the sense of limited visibility and access to prevent things like harassment and brigading, not private in the sense you’re thinking. This is not a security feature, it’s an asshole prevention feature.
I may know where the problem lies there…
I’ll see what I can do about getting it squared away today.
Somehow !gardengrooves@walledgarden.xyz doesn’t make the list, THE FIX IS IN I SAY!
Kidding obviously, well done on the community and activity growth everyone!
@Sir_Kevin@lemmy.dbzer0.com carrying !loweffortmemes@walledgarden.xyz to the top this week.
Thank you!