It’s not cheap to operate a business in Canada
SamSausages
joined 1 year ago
This is very complicated to just give an answer, because:
It varies greatly based on the content. Animated compresses vastly differently than an action movie.
Varies greatly based on encoder. NEVC vs CPU etc
Varies greatly based on encoder options. I.e. -b:v -minrate -maxrate vs -rc vbr -qmin -qmaxcq values, etc
Varies greatly based on who is watching, the TV they use and their tolerance and experience.
Savings are greater at 4k than 1080p. But once you start adding HDR into the mix, you're in a whole new world.
Even the people with very discerning eyes can't agree on everything related to this topic. Wish I could just tell you do x... but you'll have to test various methods and determine what you are happy with.
or, if you just want some space savings... use some default setting that cuts it in 1/2 and forget about it.
I think in general they have lower RPM and run a bit cooler and use a little less power. That usually comes with a bit less performance.
But I'm hooked on the WD Ultrastar series. Server Grade and fast. Also has low power usage, at full tilt, mine use less than 10w each. I'm running 20 hc530's and been rock solid.
Really depends on your use case.
Unraid is wonderful and easy to use. But really has two reasons to use it:Unraid Array fits your file storage strategy. (few writes, mainly reads)You want an EZ way to get into docker and use the unraid appstore.
Other than that, you can probably find everything on Debian or Ubuntu. (I prefer Debian for services)
You can add one more:
Proxmox and then run a Debian VM for docker, for example, and compartmentalize other things you may want to run.
Also, download a mem test utility and run it overnight to test your hardware.
I started out self hosting everything... 20 years ago or so. Then I got swept up in the "cloud" movement and put so many things into the "cloud".
Today I'm reverting back to how I started, self hosting everything that I can.
Mainly privacy, but also because they keep changing and I don't want to have to worry about them.
I just didn't feel like it was 'my' data anymore.
I do this with ZFS using a Keyfile and a script that runs at boot to unlock/mount.
I put the keyfiles on a USB drive. (Make sure you have backups!) This USB drive is hidden, I won't go into details on how I did that, several ways to do that, you can get pretty creative.
If someone steals my server, they need to know where I hid my USB, or they won't be able to get to any of the encrypted datasets.
I'm not on the latest wifi standard, but I can still get close to 1 Gigabit on wifi6, as both my AP and receiver are 4x4. I'd rather have a 4x4 wifi 6 than a 2x2 wifi 6e. (4 steams of data vs 2 streams)
So you might want to look at that as well when shopping and make sure one isn't cheaper because they cut corners on that!
Can be safer. Can be worse.
A poorly configured self hosted vaultwarden can be a major security issue.
A properly configured one is arguable safer than hosting with a 3rd party. Lastpass taught me that one.
If you configure it to where it's not exposed to the web, and only accessed through a VPN, like Tailscale. It can be quite robust.
chuckle, butthurt downvotes but not one comment to dispute anything I said. Enjoy the depreciated OpenSSL without security updates.
No, I like pfsense because it has less frequent updates and is better documented.
Here is one of the better guides that helps you config much of what you are talking about:
https://nguvu.org/pfsense/pfsense-baseline-setup/
Plus, opensense gets most of their code from the work done by pfsense, and often have to wait on them to push the code. Just look at what happened with TLS 1.3
I do this at the file system level, not the file level, using zfs.
Unless the container has a database, I use zfs snapshots. If it has a database, my script dumps the database first and then does a ZFS snapshot. Then that snapshot is sent via sanoid to a zfs disk that is in a different backup pool.
This is a block level backup, so it only backs up the actual data blocks that changed.
view more: next ›
Storage