• 34 Posts
  • 529 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • keep it on cache since I do a lot of code compilation, but I will usually switch it to frequency for gaming and stuff.

    Isn’t gaming the most cache-heavy CPU workload there is? The X3D CPUs have consistently topped gaming benchmarks, even outperforming much more modern CPUs that lack 3D cache.

    I’d sooner do it the other way around: frequency for compiling, rendering, transcoding, etc. Cache for gaming!



  • It’s not something to be proud of, that’s obvious.

    But Rutte was not made secretary-general because of his personal pride. I wasn’t happy to have him as prime minister, at all, for all those years, but he is very good at one thing: getting everyone in the room to agree and making everyone in the room feel heard.

    This is how you get Trump to be enthusiastic about your project. He is using Trump’s ego to get him om board with NATO. This is top-tier manipulation, and it’s working!

    Rutte is the perfect man for this job, and this is exactly why. No pride, no ego, just doing whatever it takes to keep the unity in NATO and to ensure we are strong enough to deter Russia.








  • The problem with non-PLP drives is that Rook-Ceph will insist that its writes get done in a way that is safe wrt power loss.

    For regular consumer drives, that means it has to wait for the cache to be flushed, which takes aaaages (milliseconds!!) and that can cause all kinds of issues. PLP drives have a cache that is safe in the event of power loss, and thus Rook-Ceph is happy to write to cache and consider the operation done.

    Again, 1Gb network is not a big deal, not using PLP drives could cause issues.

    If you don’t need volsync and don’t need ReadWriteMany, just use Longhorn with its builtin backup system and call it a day.


  • I tried Longhorn, and ended up concluding that it would not work reliably with Volsync. Volsync (for automatic volume restore on cluster rebuild) is a must for me.

    I plan on installing Rook-Ceph. I’m also on 1Gb/s network, so it won’t be fast, but many fellow K8s home opsers are confident it will work.

    Rook-ceph does need SSDs with Power Loss Protection (PLP), or it will get extremelly slow (latency). Bandwidth is not as much of an issue. Find some used Samsung PM or SM models, they aren’t expensive.

    Longhorn isn’t fussy about consumer SSDs and has its own built-in backup system. It’s not good at ReadWriteMany volumes, but it sounds like you won’t need ReadWriteMany. I suggest you don’t bother with Rook-Ceph yet, as it’s very complex.

    Also, join the Home Operations community if you have a Discord account, it’s full of k8s homelabbers.


  • F04118F@feddit.nltoMechanical Keyboards@lemmy.mldeleted
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    8 days ago

    I don’t have experience with any of the models you’re considering. I used a Corsair for years (don’t!) and am currently quite happy with an old Filco Majestouch 2 TKL that I added some white and pink keycaps to.

    The Filco was bought used, is built like a tank and only cost about €80.

    The one thing I miss in it is QMK/VIA support.

    As I understand it, a keyboard with QMK or another firmware with VIA support essentially allows you to program your keyboard however you want. And then bring that programming (“layout”) with you to another board.

    My Filco has 4 dip switches on the back that allow very limited programming: for example, switching Esc and `, or switching Caps Lock and Ctrl.

    But I can’t make it such that Caps Lock works as Caps Lock when long-pressed alone, but as Ctrl when struck in a chord with another key. QMK/VIA would make this possible.

    Even if you don’t want to do this now, having the option to play with combination keys and smart layouts like that is very interesting when you want to downsize from TKL to a smaller board.

    Also, consider the used market.