Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Technobabble by Klee from @kleegeek

David Klee is all around geek who loves data - including the platform it resides on, virtualizing it, improving performance, availability, and disaster recoverability, and data presentation and visualization. He frequently advises organizations on the techniques of migrating their business-critical physical SQL Servers to the VMware infrastructure in his day job as Solutions Architect. David speaks at many national SQL Saturday events and SQL Server User Group meetings, as well as writes technical columns on SQL Server and virtualization topics on various blogs. He is on Twitter (https://twitter.com/kleegeek), LinkedIn (http://www.linkedin.com/in/davidaklee), and blogs frequently (http://www.davidklee.net).

VMware vSphere 5.5 details trickling out

VMworld 2013 is this week in San Francisco, and some exciting details about the next version of the vSphere suite, version 5.5, are starting to trickle out. 

From my perspective, the biggest announcements so far are as follows:

  • The maximum size per VMDK and RDMv disk is now 62TB (up from 2TB) 
  • 128 vCPU and 2TB vRAM maximum per VM
  • Up to 30 devices per controller (up from 14), and up to four controllers, for a total of 120 disks total connected to a VM. This means you could do up to 7.4 PB of virtual disk-based storage connected to a single VM!
  • vSphere Flash Read Cache – host-level SSD caching for VM read activity
  • True software-defined storage in the new announcement of the VSAN (VMware blog tag here). They expect it to be released in the first half of 2014.

You can read more about these changes in the whitepaper from VMware called What’s New in VMware vSphere 5.5 Platform. Check it out! I am exceptionally excited about these features and how it can continue to improve the virtualized database server experience!

Comments

Leave a comment on the original post [www.davidklee.net, opens in a new window]

Loading comments...