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

help-circle

  • First: there is no cheap way to back this amount of data up. AWS Glacier would be about $200/mo, PLUS bandwidth transfer charges, which would be something like $500. R2 would be about $750/mo, no transfer charges. So assume that most companies with some sort of whacky, competing product would be billed by either of these companies with you as a consumer, and you can figure out how this is the baseline of what you’ll be getting charged from them.

    50TB of what? If it’s just readily available stuff you can download again, skip backing that up. Only keep personal effects, and see how much you can reduce this number by.



















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