Admin: lemux

Issues and Updates: !server_news

Find me:

mastodon: @minnix@upallnight.minnix.dev

matrix: @minnix:minnix.dev

peertube: @minnix@nightshift.minnix.dev

funkwhale: @minnix@allnightlong.minnix.dev

writefreely: @minnix@tech.minnix.dev

  • 43 Posts
  • 100 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle


  • minnix@lemux.minnix.devtoSelfhosted@lemmy.worldAnyone running ZFS?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    29 days ago

    There is no way to get acceptable IOPS out of HDDs within Proxmox. Your IO delay will be insane. You could at best stripe a ton of HDDs but even then one enterprise grade SSD will smoke it as far as performance goes. Post screenshots of your current Proxmox HDD/SSD disk setup with your ZFS pool, services, and IO delay and then we can talk. The difference that enterprise gives you is night and day.







  • minnix@lemux.minnix.devtoSelfhosted@lemmy.worldAnyone running ZFS?
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    1 month ago

    Yes I’m specifically referring to your ZFS pool containing your VMs/LXCs. Enterprise SSDs for that. Get them on ebay. Just do a search on the Proxmox forums for enterprise vs consumer SSD to see the problem with consumer hardware for ZFS. For Proxmox itself you want something like an NVME with DRAM, specifically underprovisioned for an unused space buffer for the drive controller to use for wear leveling.












  • I did something similar when migrating to 8. Consumer SSDs suck with proxmox so I bought 2 enterprise SSDs on Ebay before the migration and decided to do everything at once. I didn’t have all the moving parts you did though. If you have an issue, you will more than likely not be able to pop back in the old SSDs and expect everything to work as normal. I’m not sure what you’re using to create backups but if you’re not already I would recommend PBS. This way if there is an issue, restoring your VMs is trivial. As long as that PBS is up and running correctly (makes sure to restore a backup before making any changes to make sure it works as intended) it should be ok. I have 2 PBS’s. One on and off site.

    PBS will keep the correct IPs of your VMs so reconnecting NFS shares shouldn’t be an issue either.





  • I’ve ran jitsi for 4 years now. You can keep your personal variables in an environment file that doesn’t really change and pull down a new compose file whenever you want to update. Ever since the switch to docker from native install it has made things much easier to maintain. I’m using a lxc with debian 12. 4 cores and 4gb ram. The only reason I’ve allocated that many resources is because we use it to record a podcast with anywhere from 4 to 10 people on the server at a time. As far as bitrate, resolution, etc, that’s all handled within your env file. You’d have to look at the docs to see what’s available for you to choose from.