35
What are the hardware requirements for hosting a Lemmy instance for a single account? (lemmy.world)
submitted 3 years ago* by to c/selfhosted@lemmy.world
28 comments fedilink hide all child comments
 

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
[–] 3 points 3 years ago (4 children)

If you, as the sole user, are not subscribing to dozens if not hundreds of communities, 1GB should be barely okay. As others have pointed out, it is storage that requires more attention with a Pi 4B.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 3 years ago* (3 children)

    it is storage that requires more attention

    Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I'm not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user's posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 3 years ago (2 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 3 years ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •