« VMware Virsto: A Very Smart Volume Manager For VMs | Main | Paul Maritz Explains Pivotal »

May 22, 2013



Splitting the workload up within the physical machine is something I've been promoting to anyone who will listen (not many) for years. Splitting a job across multiple hosts using something like map-reduce (or just farming out frames on a render farm) is relatively easy.

By comparison, making a a single process use all the parallel threads available to it is a LOT harder. In terms of CPU, the loss from having an abstraction layer has been close enough to zero for years. This means using it as a poor man's SMT has been acceptable. I have had a couple of video processing workloads that I virtualised without telling anyone and they definitely improved - or at least shifted the bottleneck back to the storage (again).

The comments to this entry are closed.

Chuck Hollis

  • Chuck Hollis
    Chief Strategist, VMware Storage and Availability Business Unit

    Chuck works for VMware, and is deeply embroiled in all things software-defined storage these days.

    Previously, he was with EMC for 18 years, most of them great.

    He enjoys speaking to customer and industry audiences about a variety of technology topics, and -- of course -- enjoys blogging.

    Chuck lives in Holliston, MA with his wife, three kids and four dogs when he's not traveling. In his spare time, Chuck is working on his second career as an aging rock musician.

    Warning: do not buy him a drink when there is a piano nearby.
Enter your Email:
Preview | Powered by FeedBlitz

General Housekeeping

  • Frequency of Updates
    I try and write something new 1-2 times per week; less if I'm travelling, more if I'm in the office. Hopefully you'll find the frequency about right!
  • Comments and Feedback
    All courteous comments welcome. TypePad occasionally puts comments into the spam folder, but I'll fish them out. Thanks!