• 0 Posts
  • 269 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle




  • non_burglar@lemmy.worldtoSelfhosted@lemmy.worldProxmox 9 released
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    4
    ·
    edit-2
    3 days ago

    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.
















  • 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.