this post was submitted on 10 Jul 2023
31 points (94.3% liked)

Selfhosted

40149 readers
654 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
 

I'm interested in possibly hosting my own Lemmy instance - just for my own account. I was thinking of hosting it on Raspberry Pi (possibly the 1GB Pi 4 B), but I couldn't find much for definitive information on what the hardware requirements would be for such an instance to know if this is even possible. How much storage is required? Is the Pi 4 CPU powerful enough? How much memory?

you are viewing a single comment's thread
view the rest of the comments
[–] i_lost_my_bagel@seriously.iamincredibly.gay 4 points 1 year ago (1 children)

It's caching posts from other servers so that if you have an instance with a few hundred or thousand people on it and they all open the home page you don't send out thousands of requests for each post and end up DDOSing a bunch of other servers.

[–] Kalcifer@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

I don't really understand this reasoning. Some server would still need to receive those requests at some point. Would it not be better if those requests were distributed, rather than pounded onto one server? If you have a server caching all the content for its users, then all of its users are sending all of those requests for content to that one single server. If users fetched content from their source servers, then the load would be distributed. The only real difference that I can think of is that the speed of post retreival. Even then, though, that could be flawed, as perhaps the source server is faster than one's host server.

[–] KairuByte@lemmy.world 1 points 1 year ago

The data does get pulled, but only if it is “old.” If you just pulled 0.5 seconds ago, you don’t even need to check.