N100, 16gb ddr4, m.2 ssd
N100, 16gb ddr4, m.2 ssd
You’re free to have that opinion, and I share it personally.
However, self-hosting doesn’t have to be all-or-nothing, and some ppl have requirements that make cloudflare a sensible option.
Whoah, I see this has indeed changed. Thanks.
Edit2: the following is no longer true, so ignore it.
Why do you want this? There are very few valid use cases for it.
Edit: this is a serious question. Adding a member to a vdev does not automatically move any of the parity or data distribution off the old vdev. You’ll not only have old data distributed on old vdev layout until you copy it back, but you’ll also now have a mix of io requests for old and new vdev layout, which will kill performance.
Not to mention that the metadata is now stored for new layout, which means reads from the old layout will cause rw on both layouts. It’s not actually something anyone should want, unless they are really, really stuck for expansion.
And we’re talking about a hypervisor here, so performance is likely a factor.
Jim Salter did a couple writeups on this.
Your settings are not 1 to 1 on both systems, you’ll have to identify what “auto” means in each context, it’s variable depending on where ffmpeg lives.
2nd for alpine, it’s what I use for my wg
If you’re gonna use use the ogg container, you might as well use the newer opus compression.
Are you looking for an android app to control radarr and sonarr, or to control an nzb backend? They have different functions.
I do, but only for work. There are certain tasks you can’t do easily with just api calls.
The 720 is not going to benefit from power savings, even going to hot-spare for the power supplies. These things are relics from the time when power was cheap.
I couldn’t get my r720 down below 160w, which is unacceptable for just running some containers.
I have 5x1080 streams to my frigate container and it only has a coral tpu passed through, 4 to 8% CPU usage in the container. The arc will not yield any advantage unless op is using vino to run the ml, but they pointed out that they are getting a coral tpu.
Rsync in a cron job would do it, no?
Finally retired proxmox (actually I just removed pve packages and repos). Left the nfs export on there and hardened the whole thing.
Now I’m slowly working to get all my installs into layered ansible playbooks. Fortunately, there exists an incus ansible module.
With separate, mounted, persistent data, it’s getting very close to docker in easy deployment.
“Ghost”… That brought back memories, thank you.
Good story. And boy, I’m jealous of your first time, I wish I could go back, in a way. Keep going, it gets better.
Whether your ip changes frequently depends on your ISP, but it’s not necessary to have a static ip. My public IP changes about once a year, but I use my router to update my dns and make ally external services rely on DNS and not IP to connect.
You can also do this, look up “dynamic DNS”. You just need to register a DNS name (can be free) and set up the updates to make it accurate.
I checked the specs on 5 modern, newly released IP cameras. They all use h264/h265, aka AVC1 and HVEC. Not surprising, cause that’s part of the spec.
I’m angrily going to go look because you’ve introduced doubt in my mind. And I don’t like not knowing.
You just went on about how easy nix is to configure, then about adding bluetooth devices, then jumped to installing ableton on windows.
Op specified they are a musician using a studio distro for studio tasks. You didn’t address any of that.
I get that you’re impressed with nix and want to share, and nothing wrong with that. But let’s at least stay on topic.
You are mistaken. Frigate ingests rtsp and direct streams using HLS, which only accepts h264 or h265. The vast majority of cameras encode in h264. H264 is a trivial decode operation on modern hardware within the last decade.
I am currently looking at CPU usage in my frigate container with 5 1080p RTSP streams and it is hovering at between 4% and 8%. Without any quicksync configured, just CPU and coral.
I don’t know what your deal is, or why you think you know more than folks who have been doing this for years, but stop, please. You don’t know what you’re talking about.
And I have some container updates to test!