this post was submitted on 15 Feb 2024
65 points (97.1% liked)

Selfhosted

40296 readers
271 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
 

Here is the thing, I have 4 RPi’s of different generations (all the way from Zero W to 4B 4GB) that I use to host services at home for personal use.

Lately, I have realized I am running out of RAM to host more services, not to mention not enough switch ports to connect to.

Now I know the obvious solution is to get a more powerful setup (maybe a thin client) but electricity isn’t cheap and I am not particularly in the best shape financially speaking to shell out $300+ on a decent client to host my services.

Any suggestions?

you are viewing a single comment's thread
view the rest of the comments
[–] bastion@feddit.nl 3 points 9 months ago (1 children)

If you don't already use it, zram swap is great for providing a little bit extra oomph. If your server doesn't have a lot of compressed data in memory, it can literally more than double your effective ram.

[–] admin@lemmy.mohammadodeh.com 1 points 9 months ago (1 children)

Doesn’t swap reduce the lifespan of storage though?

[–] bastion@feddit.nl 4 points 9 months ago (1 children)

Zram swap is basically this: Turn all of your free ram into a swapdisk. Compress all access to that swapdisk.

So, it's not using you storage, buy your memory. Most stuff in memory is usually highly uncompressed - so it compresses really well.

Instead of getting the additional space from disk, it's getting it from compression.

[–] admin@lemmy.mohammadodeh.com 1 points 9 months ago (3 children)

Can you please explain to me the difference? How does a swapdisk compare to RAM? I don’t mind googling it but I highly doubt I’ll get a straightforward ELI5 style answer from there.

I would really appreciate it if you can elaborate, if you have the time that is.

Thank you.

[–] ryannathans@aussie.zone 2 points 9 months ago

It just compresses your ram contents so you can fit more stuff in memory at once

[–] Gooey0210@sh.itjust.works 2 points 9 months ago

Basically zram is compression inside ram

[–] bastion@feddit.nl 2 points 9 months ago* (last edited 9 months ago) (1 children)

There are two types of computer memory that fundamentally matter on the consumer level:

  • memory, as in RAM, which is like short-term memory in people, or how much you can think about at once. It is blanked when the computer restarts. It is very fast.
  • drive storage, as in hdd or ssd space. This is like long-term memory or overall knowledge capacity, and persists across boots. It is comparatively slow.

Solid state disk storage, and in particular some SD cards, can be vulnerable to excessive writes.

Ram, however, is not impacted by the number of uses.

A swap file works like this: When memory gets full, you move the least-used parts onto the swap file.

A normal swapfile is on-disk. When memory gets close to full, the system moves some onto the (much much slower, like 10-1000x) on-disk swapfile.

Zram swap creates a compressed swapfile out of your free memory. A file in linux does not have to be on a hard disk/ssd, it just has to look and quack like a file. When memory gets close to full, the system copies some onto the in-memory compressed file. This is very fast, but uses some cpu. It doesn't touch your drive storage.

[–] admin@lemmy.mohammadodeh.com 2 points 9 months ago

That is a great explanation. It makes perfect sense to me know. Thank you