8
[email protected] is for open-ended questions, not questions regarding lemmy :)
Looked over your other post,
Your instance A replicates or really caches the content from C@B indefinitely, if you are subscribed to it (or if anyone on your instance is subscribed). When you make a post on C@B your instance transmits that post data to B. Other instances subscribed to C@B will get your post when they receive cache updates. As long as the instances aren't overloaded it is a pretty snappy process in my experience.
Pictures are not replicated but hosted on the instance of the user posting them. Post/Comment data is cached. Your instance will store a cache of all the subscribed communities. Even with a large number of subscriptions all that data is just text and gets filed into the database without consuming much space at all.
Edit: just some things I've read while setting up my instance. Pretty sure that's accurate.
Thanks! That clears things up a bit.
So all text and metadata is kind of replicated but "heavier" stuff only resides on the original instance.
Your instance will store a cache of all the subscribed communities
I'm assuming more the number of communities, more the instance has to periodically probe and retrieve cache updates. Hopefully these are just deltas, so the updates are small.
However, for large instances, these periodic updates can become resource-hungry activities
Hey, accidentally deleted my post instead of editing, oops.
It will have more work to do to keep a larger number of communties in sync however that part is actually pretty efficient. It sends just the bare minimum data in a json like format. If you have an instance you can watch the log and see them ticking along, getting and posting.
The majority of system load is from the UI. Database query's to build a users home page and feeds. At least all those query's will hit the local instances cache and spread out the load.
view more: next ›
this post was submitted on 13 Jun 2023
8 points (90.0% liked)
Selfhosted
37809 readers
513 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:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS