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

help-circle

  • You might want to check what the actual hardware is first. You’ll probably be fine, but client 802.11 hardware can sometimes be underwhelming for hosting because they don’t have good stuff like beefed up MuMIMO.

    Although that’s assuming you will have a lot of traffic going through it, so you could always just test throughput and latency with iperf to see how well it functions.


  • mlg@lemmy.worldtoSelfhosted@lemmy.worldSelf host websites
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    It depends on what it is really + convenience. There are lots of morons out here running basic info sites on full beefy datacenter VMs instead of a proper cloud webhost service.

    The most you’d be getting out of cloud is reliability. Self host assumes you don’t have any bottlenecks (easy enough to pass), but also 99% uptime which is impossible unless you are running with site redundancy (also possible, but I doubt how many people own multiple properties with their own distribute or private cloud solution).

    if 95% uptime is acceptable, and you don’t live in an area with outage issues from weather, I’d say go for it. Otherwise, you can find some pretty cheap cloud solutions for basic websites. Even a cheapo VPS would probably work just fine.


  • I have run photoprism straight from mdadm RAID5 on some ye olde SAS drives with only a reduction in the indexing speed (About 30K photos which took ~2 hours to index with GPU tensorflow).

    That being said I’m in a similar boat doing an upgrade and I have some warnings that I have found are helpful:

    1. Consumer grade NVMEs are not designed for tons of write ops, so they should optimally only be used in RAID 0/1/10. RAID 5/6 will literally start with a massive parity rip on the drives, and the default timer for RAID checks on Linux is 1 week. Same goes for ZFS and mdadm caching, just proceed with caution (ie 321 backups) if you go that route. Even if you end up doing RAID 5/6, make sure you get quality hardware with decent TBW, as sever grade NVMEs are often triple in TBW rating.
    2. ZFS is a load of pain if you’re running anything related to Fedora or Redhat, and the performance implications from lots and lots of testing is still arguably inconclusive on a NAS/Home lab setup. Unless you rely on the specific feature set or are making an actual hefty storage node, stock mdadm and LVM will probably fulfill your needs.
    3. Btrfs has all the features you need but is a load of trash in performance, highly recommend XFS for file integrity features + built in data dedup, and mdadm/lvm for the rest.

    I’m personally going with the NVME scheduled backups to RAID because the caching just doesn’t seem worth it when I’m gonna be slamming huge media files around all day along with running VMs and other crap. For context, the 2TB NVME brand I have is only rated for 1200 TBW. That’s probably more then enough for a file server, but for my homelab server it would just be caching constantly with whatever workload I’m throwing at it. Would still probably last a few years no issues, but SSD pricing has just been awful these past few years.

    On a related note, Photoprism needs to upgrade to Tensorflow 2 so I don’t have to compile an antiquated binary for CUDA support.






  • mlg@lemmy.worldtoLinux@lemmy.mlDo you use Gnome or KDE Plasma?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    3 months ago

    KDE for best fully integrated, out of box, modern DE.

    XFCE + Compiz if you’re running on lower end hardware (uses less ram and utilizes gpu better). Also if you want even more customization than KDE with the drawback of limited SVG support (and still on X11 if that matters for you)

    GNOME if you hate yourself and want to use a knockoff of ChromeOS or Mac.

    Cinnamon and MATE if you want to see when GNOME used to be good.

    LXQt is the XFCE equivalent of KDE, but is now on wayland with GPU accel, so it can fit the same area as XFCE+Compiz.

    Wayfire (compositor) basically Compiz for Wayland if you want all the fancy effects on anything that uses wayland.





  • XFCE + Compiz

    The unholy combination of accelerated 3D graphics and performance, all without the stupid drawbacks of wayland.

    Runs much lighter than KDE even with all the 3D cube and windows stuff enabled.

    Extremely customizable as well. XFCE already does a great job of UI/UX, it just lacks a compositor to add flare (xfwm4 has no animations, only some blur effects).



  • I don’t know why the guy just assumed every linux and BSD machine runs cups-browsed by default?

    It took me literally 5 seconds to check that it’s disabled on Fedora by default.

    Then he wrote a whole paragraph about how no one should use CUPS for printing because based off of his own analysis, it’s some insanely crappy and insecure system.

    Which is actually stupid because the only alternative is windows??? Which is universally known for printer driver and spooler vulnerabilities.

    Then he got mad the the maintainer for patching before his disclosure…


  • People fear the same thing about Valve.

    One wrong person and we could all end up in the same money milk machine as EA.

    I know people complain about Linus hurling insults at merge requests, but his rigidness is what keeps the kernel viable. If it weren’t for him, google would have already shit all over it with a mega fork and essentially cornered the market like they did with Android and HTTP3.

    Both are technically “open source”, yet Google essentially dictates what they want or need for their economic purpose, like ignoring JPEGXL, forcing AVIF, making browsers bloaty, using manifestv3, etc. Android is even worse and may as well be considered separate from Linux because it’s just google’s walled garden running on the linux kernel.

    He is open to new technology, but he understands the fundamental effects of design choices and will fight people over it to prevent the project from fracturing due to feature breaking changes, especially involving userspace.