Hey all,

I know this is a bit off-topic but this sub is one of the few where one can talk about technical stuff and not about tech careers lol.

I have been thinking about that a lot lately. Are there use cases where bare metal is better than virtualization? Have you ever encountered an use case that the virtualization overhead is an issue? I would love if you share your experiences. Thanks =)

  • epsiblivion@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    for selfhosting stuff, I don’t see any requirements to be bare metal. the exception is the router/firewall. if you want to do software for that, then at least have a dumb all in one router as a spare when you inevitably break something and have family waiting on you to get the network back up. in an enterprise network, i would 100% keep networking physical. only keep physical server for applications that need every ounce of performance.

    • nyrosis@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      This…

      It’s good to have the router/firewall as it’s own device. An argument could be made for a NAS too simply doing NAS functions.

      For servers I see no point because in the home environment you can squeeze more out of the system using a hypervisor. Even in an enterprise environment you are likely thinking about clustering/HA which still will be utilizing a hypervisor.