this post was submitted on 19 Jun 2023
36 points (100.0% liked)

Selfhosted

40730 readers
324 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 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
36
Missing comments from subscribed community on another instance? (jamie.moe)
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/selfhosted
32 comments fedilink hide all child comments
 

I do the majority of my Lemmy use on my own personal instance, and I've noticed that some threads are missing comments, some large threads, even large quantities of them. Now, I'm not talking about comments not being present when you first subscribe/discover a community to your instance, in this case, I noticed it with a lemmy.world thread that popped up less than a day ago, very well after I subscribed.

At the time of writing, that thread has 361 comments. When I view the same thread on my instance, I can see 118, that's a large swathe of missing content for just one thread. I can use the search feature to forcibly resolve a particular comment to my instance and reply to it, but that defeats a lot of the purpose behind having my own instance.

So has anyone else noticed something similar happening? I know my instance hasn't gone down since I created it, so it couldn't be that.

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

Does your server have enough power and workers to handle all the federated messages? Or is it constantly at 100% CPU?

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

The machine is a dedicated server with 6 cores, 12 threads, all of which are usually under 10% utilization. Load averages currently are 0.35 0.5 0.6. Maybe I need to add more workers? There should be plenty of raw power to handle it.

[–] [email protected] 5 points 2 years ago (2 children)

Yeah that sounds about enough to handle the load. How many workers do you use? And do you see any errors in your logs about handling messages? You could try to search for that particular thread to see if all replies are handled correctly?

[–] [email protected] 5 points 2 years ago

Update: Did a -f watch of the logs for WARN messages while upping worker counts. Seems 1024 was the sweet spot. Upped further to 1500, and the warnings for expired headers have entirely stopped in large part. So it seems this was the solution.

Thanks for your help!

[–] [email protected] 3 points 2 years ago

I had it at the default 64, but I'll try 512 and see if that helps. Nginx is configured to use 768, so I doubt there's any bottleneck there. I did notice in the troubleshooting page there's mention of searching the logs for "Activity queue stats," but a grep of the docker log shows no results for that string.