I got 32 additional GB of ram at a low, low cost from someone. What can I actually do with it?

    • slazer2au
      link
      English
      175 days ago

      One docker container per VM just to maximise the ram usage.

      • Onno (VK6FLAB)
        link
        fedilink
        175 days ago

        I realise that you are making a joke, but here’s what I used it for:

        • Debian VM as my main desktop
        • Debian VN as my main Docker host
        • Windows VM for a historical application
        • Debian VM for signal processing
        • Debian VM for a CNC

        At times only the first two or three were running. I had dozens of purpose built VM directories for clients, different hardware emulation, version testing, video conferencing, immutable testing, data analysis, etc.

        My hardware failed in June last year. I didn’t lose any data, but the hardware has proven hard to replace. Mind you, it worked great for a decade, so, swings and roundabouts.

        I’m currently investigating, evaluating and costing running all of this in AWS. Whilst it’s technically feasible, I’m not yet convinced of actual suitability.

        • @[email protected]
          link
          fedilink
          English
          85 days ago

          costing running all of this in AWS

          The cost will be oh, so much more than you’re expecting. I have not been at a shop where they didn’t later go “oh shit. Repatriate that stuff so it doesn’t cost us a mint.”

      • @[email protected]
        link
        fedilink
        75 days ago

        I unironically do this in proxmox. Keeps things nice and separate and i still have plenty ram left.

        • slazer2au
          link
          English
          25 days ago

          Any reason for not using LXC as PX has native support?

          • Onno (VK6FLAB)
            link
            fedilink
            55 days ago

            In my case, I’m not a fan of running unknown code on the host. Docker and LXC are ways of running a process in a virtual security sandbox. If the process escapes the sandbox, they’re in your host.

            If they escape inside a VM, that’s another layer they have to penetrate to get to the host.

            It’s not perfect by any stretch of the imagination, but it’s better than a hole in the head.