In 2008, the year before I left VMware, I was invited to help measure the amount of information being enterprise computers processed in the entire year. My invitation came from Dr. James Short of the University of California, San Diego, who was on the team leading this project. The team called their project “How Much Information?” (HMI). And Dr. Short, or Jim, wanted me to provide comment on a small portion of the systems that process information: enterprise hardware.
Scott Drummonds on Virtualization
Bryan Semple at VKernel last week wrote a blog article on per-VM pricing in VMware and VKernel products. Bryan observed that VMware’s customers dislike per-VM pricing. He then stated that VKernel will stick to asset-based pricing such as per-socket. Bryan spends a lot of time with customers and I will not refute his claims. Whether or not we like per-VM pricing, I think it is here to stay.
SPEC has diligently working on an industry standard version of VMmark since something like 2006. The first version of their product is complete and was released during my recent holiday. I have been talking with colleagues and customers about SPECvirt for years and would like to talk about what SPECvirt is and what it is not.
I continue to receive many questions from our customers on the expected performance gains of the new version of Hyper-Threading in Intel’s Core i7 processors. The answer requires a little bit of discussion on Hyper-Threading, a little bit on ESX, and comes with some performance data. If you are still interested, read on.
I love VMware’s performance blog, VROOM! It is our most popular performance communication vehicle and its content is backed by a stellar engineering team with unmatched integrity. Each article details the nuances of VMware performance and educates on application and platform best practices. I love all the articles but am always surprised as to which our readers find most popular. Here is a countdown of the five entries most read in 2009.
[This is the last re-post of old community content. But this content is important enough to be worth a re-post.]
I spend a great deal of time answering customers’ questions about the scheduler. Never have so many questions been asked about such an abstruse component for which so little user influence is possible. But CPU scheduling is central to system performance, so VMware strives to provide as much information on the subject as possible. In this blog entry, I want to point out a few nuggets of information on the CPU scheduler. These four bullets answer 95% of the questions I get asked.