63
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 May 2024
63 points (97.0% liked)
Selfhosted
39677 readers
302 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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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
It depends what your parameters are. For spinning hard disks, you want to look at total power cycles, and mean time between failures. More enterprise drives have very long mean time between failures
In fact for spinnig hard disks, turning on can be on a likely failure mode, so there's machines out there if you power off there's a good chance they won't come back on in the enterprise data centers
Your solid state hard disks, you want to look at meantime between failures, but also total write volume. Enterprise discs tend to have much much much much much much greater write capacity
So all of these trade-offs cost money, if you're looking at archival, where you write the data only once, then you can go with a disk that has a low total write volume