this post was submitted on 03 Aug 2025
29 points (91.4% liked)

Selfhosted

50178 readers
443 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
 

I tried to find a more applicable community to post this to but didn't find anything.

I recently set up a NAS/server on a Raspberry Pi 5 running Raspberry Pi OS (see my last post) and since then I've got everything installed into a 3D printed enclosure and I've got RAID set up (ZFS RAIDz1). Prior to setting up RAID, I could transfer files to/from the NAS at around 200MB/s, but now that RAID is seemingly working things are transferring at around 28-30 MB/s. I did a couple searches and found someone suggesting to disable sync ($ sudo zfs set sync=disabled zfspool). I tried that and it doesn't seem to have had any effect. Any suggestions are welcome but keep in mind that I barely know what I'm doing.

Edit: When I look at the SATA hat, the LEDs indicate that the drives are being written to for less than half a second and then there's a break of about 4 seconds where there's no writing going on.

you are viewing a single comment's thread
view the rest of the comments
[–] Creat@discuss.tchncs.de 3 points 2 days ago* (last edited 2 days ago) (5 children)

What size is the ARC set to? I've seen cases where it was fully disabled, which (unsurprisingly) seemed to murder performance and is probably even worse when in such a CPU limited platform. You stating that only 1.5 GB of 16 GB were in use makes this seem likely.

In general, if you care even remotely about performance, a raspberry pi is probably the wrong choice for a NAS. Even a single disk should have no issues saturating a 1gbe link. That being said, even a pi should manage 1 GBit/s on ZFS, especially when reading.

[–] ramenshaman@lemmy.world 3 points 2 days ago* (last edited 2 days ago) (4 children)

I don't know what ARC is and my searches so far haven't helped. The CPU usage is pretty low, on htop is rarely passes 10%.

Edit: I asked chatGPT what it means, this seems like exactly the setting I was hoping to find. I'll check it out and post an update.

Edit2: I changed the ARC size to 8GB and it definitely seems to have gotten slower.

[–] Creat@discuss.tchncs.de 2 points 2 days ago* (last edited 2 days ago)

ARC is the in-memory cache used by ZFS. If it's completely off the effect can be dramatic. Under no circumstances should a larger cache cause anything to get slower, ever. Even the raspi didn't have memory that is that slow that this is a reasonable outcome. By default on most distros, ARC size is capped to 50% of physical system memory. Keep in mind it is a cache: if something else needs needs the RAM, it will be released.

As a concrete example: I was recently working on a server where a maintenance task that should take like 12hrs or so at the worst somehow took 2 weeks (!) and still wasn't finished. That was ARC being disabled.

load more comments (3 replies)
load more comments (3 replies)