The problem during VDI Boot storms is that while booting, each VDI VM needs to read large areas of the disk where the OS is stored and during certain times such as employees coming to work in the morning the VDI VM boot ups can all happen around the same time. Occasional high disk usage can easily be handled if these spikes are random and not synchronized across many VDI VMs. Typically, VDI users require low storage IOPS for normal work, but that’s only after the VM has booted up. The problem is aggravated by the resource requirements which are peculiar to VDI deployments. This results in storage becoming a performance bottleneck in any high load situation such as VDI Boot Storms. While Storage speeds have gone up significantly in the last 10 years with the widespread availability of SAS and NVMe SSD based storage, the price-performance increases in storage speeds have still lagged behind other computing resources such as CPU, Memory and Networking. Virtual Desktop Boot Storms caused by Storage Bottlenecks With servers now having multicore and faster CPUs, 100s of GBs of RAM, and 10gbps networking, many computing resource pressures have gone away, but contention for storage IOPS continues to plague VDI deployments. This led to many initial VDI deployments being abandoned and the technology almost not taking off. This problem has been faced by VDI deployments ever since they were introduced way back in 2007-08. When a large number of VDI VMs are simultaneously powered on and their OSes boot up it puts enormous stress on various computing resources – CPU, Memory, Networking and Storage. Boot storms are caused when many VDI users simultaneously boot up their virtual desktops, say first thing in the morning when they come to work. VDI deployments are plagued with boot storm problems as they scale up.
0 kommentar(er)
