• 501 Posts
  • 4.35K Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle



  • What might simplify your thinking about this is called “Semantic Versioning”.

    You have a big codebase of all kinds of features, but at a certain time you want to release it to be able to differentiate between a point in time and release number so you can tell when a regression happens and address it.

    Proton is released by version to be able to see this exact thing. They keep all the old versions available for users because they know that not every single point release will work for all games, and there will be regressions.

    This allows users to be able to identify a stable working version of Proton for a specific game, and stick to it. If you try to upgrade for a newer release for some reason and find a problem, you can always go back to the previous working version and know for certain it will work without issues.

    For your specific scenario, just check ProtonDB for games and see if people have posted tweaks and config combos for a specific game. Great resource for this exact reason.






  • It starts with the hardware first. You started well with tuning your CPU/MEM frequency settings, but that matters less if you’re running giant PSUs (or redundant), more drives than you need, and a huge number of peripherals.

    Get a cheap outlet monitor to see what your power draw is and track it at the wall. I just got these cheap Emporia ones. I’m sure there’s more reputable ones out there.

    Don’t go crazy with your networking solution if you don’t need them. PoE switches draw tons of power even when idle, and a 24-port switch is a huge draw if you’re only using 3 of them.

    Consider getting a power efficient NAS box for backend storage, and low power Minipc for frontend serving instead of using a power hungry machine for all your network apps.

    You can dive deeper into any angle thing, but these are the basics.