Best Practices for Deploying MinIO in Virtualized Environments

Re:Best Practices for Deploying MinIO in Virtualized Environ... by phreenet on Thursday January 20, 2022 @02:04PM (#30013125)

> Avoid “noisy neighbor” problems. In order to get the most from MinIO, it should be the only workload running on the hypervisor, the same as you would do for any high performance system in a virtualized environment. This will prevent loss of performance caused by resources being consumed by workloads as they run on other VM’s.

I understand their logic behind this but if MinIO is best used as the only VM on an entire physical system why bother with running it on a hypervisor? I guess "single pane of glass management" but why bother with the license cost of VMware, RHEL, etc.?

[ Parent | on HN ]

Re:Best Practices for Deploying MinIO in Virtualized Environ... by alar44 on Thursday January 20, 2022 @04:53PM (#30015657)

If I listened to all of my vendors when they say this I'd have 12 physical servers rather than 2. This is nonsense as long as you pay attention to your loads.

[ Parent | on HN ]

Re:Best Practices for Deploying MinIO in Virtualized Environ... by SteveNuts on Thursday January 20, 2022 @03:07PM (#30014003)

You still get hardware redundancy by clustering the hypervisors together, so you could start your VM workload up on a healthy node.

[ Parent | on HN ]

Re:Best Practices for Deploying MinIO in Virtualized Environ... by vorpalhex on Thursday January 20, 2022 @04:08PM (#30015030)

You can backup the entire vm and shift it to new hardware when you have a hardware failure. If you are already doing a lot of VMs, you continue using the same monitoring and deployment for everything.

[ Parent | on HN ]

Re:Best Practices for Deploying MinIO in Virtualized Environ... by habitue on Thursday January 20, 2022 @02:06PM (#30013149)

Maybe something like https://firecracker-microvm.github.io/ ?

[ Parent | on HN ]