Home > Intel Communities > Open Port IT Community > The Server Room > Blog > 2008 > October > 03
0

For those of us who have lived through the cyclical nature of Enterprise technology innovation, the last month has seen the public and private backlash of an "emerging" compute models, known as Cloud Computing. Industry veterans claiming marketing hype, others claiming leadership in this space and some committed to changing the landscape of computing have begun their public positioning of this new compute paradigm. So what has changed and why all the "backlash": I'll outline my thoughts, remind people of history and outline what I believe the future holds.

 

Why now?

 

1. Moore's Law, Metcalfe's Law and Buffett's law (I'll explain later).

 

A. Moore's law and the era of multi-core provides all of us in the industry the capability to grow our compute infrastructures in a more scalable, cost effective fashion then at anytime in the history of our industry. This isn't hype this is reality. We are delivering better than 2x the performance in our recently announced Intel Xeon 7400 series product than our Intel Xeon 7100 series product launched just 2 years ago. I might add that our Intel Xeon 7400 platform is the industry 1st 1 million tpm/c x86 architecture in history. Moore's law is alive and well. Perfectly suited for the Physical layer of Cloud Computing .

 

B. Ethernet performance and innovation has outstripped Fiber Channel and Infiniband in terms of innovation. This has allowed for a Gigabit revolution from Desktop to Data Center. The Gigabit revolution is driving a transformation of how communication networks are being built around the world. This law will be constant and Intel is committed to being a leader here as well.

(Note: I was the NUMA-Q systems architect for the 1st ever production fiber channel solution deployed for commercial use at the NASD in 1997 with EMC...at the time ethernet was a 10/100mb controller)

 

C. Buffett's Law: The value of an enterprise is a direct correlation of it's ability to deliver consistent return on invested capital, regardless of market conditions. Enterprises will/are being required to drive consistent returns with an intelligent, expandable and cost effective IT infrastructures. Information Technology leadership is key to all successful businesses in a global economy. Cloud computing has the potential to provide a flexible internal capability with external application growth capabilities. This is not yesterday's outsourcing models. Warren Buffett is driving change through value investing, this rewards the conservative innovator more than the flambouyant visionary of a "boom" cycle. I'm not sure he even understands the significance his investment models have begun to place on our industry...

 

2. Virtualization for x86 compute technologies. Over 80% of the world's server shipments.

 

 

A. Expansion of virtualization technologies to increase the utilization of the compute infrastructures has increased the flexibility of these environments. Introduction of flexible migration technologies for virtual machines provides meaningful cost savings for software licensing, energy efficiencies and scale for viral workloads.

 

 

B. Educating tomorrow's Web 2.0 innovators is easier on our platforms, compilers and technologies that are available in every market in the world....within state department allowed countries. :>

 

 

C. Broadband Access around the world. Wimax, 3G, Fiber to Home, xDSL and Cable...thanks!

 

 

3. Google's Law: Viral IS the market.

 

 

A. Our children fortunate enough to afford access, live in a online world where Viral isn't a sickness. Communities expand and contract based upon their ability to meet the needs of their constituency. John Stuart Mill would be proud.

B. Cloud Computing provides the necessary compute infrastructure for tomorrow's software artists to build a community in their own likeness, even the founders of Google are growing increasingly out of touch as they grow older.

 

 

What's different from the past?

 

 

1. Clusters aren't a requirement. Cluster technologies are difficult to manage, administer and unpredictable. In addition their software licensing costs have been traditionally prohibitive for wide-scale deployment across an enterprise.

 

 

2. Intel's compute requirements and capabilities are as never before. See above or visit www.intel.com

 

 

3. Client/Server architectures, Open Source and Web 2.0 have unlocked a world of programming models capable of acting different.

 

 

4. It has been 10 years since Siebel Net, the 1st Client Server ASP, was architected from a deal between Tom Seibel and Casey Powell....yes it was ground breaking and no it didn't make a lot of money....but it did spark an industry that has given us Salesforce.com, Corio, OracleOnline and others. We designed these infrastructures knowing they had meaningful limitations yet with the industry's best technology available at the time. We have had a first act.

 

5. Latency improvements has reduced virtual machine migration to minutes and application deployment models from weeks to hours. As we decrease the latencies of the physical layer from minutes to milliseconds across cpu, memory, networking and storage we are providing the basis for breakthrough programming models such as Cloud Computing.

 

 

What does the future hold?

 

My Top 9 predictions....(time for the station announcement....these opinions are not necessarily opinions of Intel, the opinion expressed below are the author.)

 

1. Cloud Computing infrastructures will provide the basis for a new compute and development infrastructures that will allow the world's smartest technologists to have access to more compute resources than they have ever been able to afford. The cloud will provide breakthrough research in the following areas in the next 5 years: DNA mapping, FDA regulation, Energy Consumption and Exploration modeling, Retail Supply Chain, High Definition Content Creation and Human Rights.

 

2. Cloud Computing will deliver the most consistent, scalable and available compute infrastructure ever created. Translation...there is failure, there is not downtime. It will also mark the end of Tape backup technologies and proprietary storage interfaces over the next decade. I'm not sure why we need clustering technology in the future either but...that is the subject for another blog.

 

 

3. Cloud Computing will make device compute capabilities even more important than they are today. The easier the access to high value content the more important the compute capabilities of the end user device to enjoy the content.

 

 

4. Cloud Computing will change the Entertainment Industry over the next 5 years. More access, more distribution, less cost, more profits with less risk.

 

 

5. Cloud computing will have the single biggest effect on traditional software licensing models of any environemental change in our industry. More of an impact than Multi-Core, Clustering or Google.

 

 

6. Cloud Computing will drive innovation and interoperability. Innovation in programming models for business and consumer applications. Interoperability across the physical, application and user interface layers of a cloud infrastructure.

 

 

7. Cloud Computing infrastructures will consume up to 50% of all x86 server CPU cycles by 2016.

 

 

8. Whichever entrepeneurs emerge as the leaders of the "Age of Cloud Computing" will be the technically most well-rounded technologists our industry has ever created. Hopefully, they will be equally well-rounded in their business planning processes.

 

 

9. Cloud Computing will begin to unearth a global data standards initiative. As an industry we will have to work with the regulatory leadership around the world to define acceptable and secure standards of data integrity across Cloud infrastructures.

 

 

For the non-believers...I must apologize. Explanations I can give, understanding I cannot. Cloud Computing is not a fad. it is a desired state of end users who face real business challenges with unpredictable compute requirements, budgets and human resources.

 

 

Where there are clouds there is usually rain.....

0 Comments Permalink
0

 

One of the common questions that I get from customers is whether their applications will be able to take advantage of so many cores in their server. And it's not just running the application without changes, but also being able to scale in performance. I would like to address this concern in three parts:

 

 

 

  • What does many cores on a server bring to me? Applications that run on x86 servers today have been written to take advantage of more processors (or SMP) on the Servers since the 90s. These applications have been threaded over time and fined tuned to deliver optimum performance. When such applications are run on a many-core platform (such as the 4-way Intel(r) Xeon(r) 7400 processor-based server), these applications show instantaneous performance gain. Database applications such Oracle 10g, IBM DB2, Microsoft SQL Server 2005, Microsoft SQL Server 2008 have shown significant performance gains when run on a 6-core Xeon 7400 processor-based server. As an example, check out the TPC-C performance of the 4P platform. We have seen SQL Server 2005 performance gains up to 68% compared to the previous generation processor - The highest 4P database performance on a Windows Server Platform today. We also have seen the highest DB2 database performance on Linux OS. Similarly, using Oracle OASB benchmark with Oracle 10g R2 DB and Oracle E-business suite v12, the IBM x3850M2 delivered unparalleled processing of 10,000 employee payroll batch update in 5.37 seconds (Wall Clock Duration). So Clearly, the benefits of using multi-core processors such as the 6-core Xeon 7400 processor are immense. It's performance and more performance all the way for enterprise workloads.

 

 

  • Do I have to get the latest version of my application to get optimum performance? In most of the cases for enterprise workloads, the application gets performance boost as more cores are added to the system. However, the performance may not be optimum. As newer tools emerge to take advantage of Intel® Core® Architecture in a parallel environment, the ISVs may make changes to their software to give the their applications additional performance boost. Tools such as compilers and libraries from Intel, Microsoft, Oracle, Sun and others are constantly updated to provide optimum scaling and performance on Intel Architecture based Servers.

 

 

  • Does my application cost more on a 6-core Xeon 7400 processor-based server? In most of the cases, NO. You need to make an assessment of the software licensing model currently used on your servers and then decide if the price/performance is worth moving to the Xeon 7400 processor-based platform. From what we have seen in the past many years, the performance of a multi-core platform far outweighs the price of the platform. In short, YOU PAY LESS TO GET MORE. Today multi-core processing has become the norm for Enterprise Applications. ISVs are constantly evaluating their application licensing models to run in an SMP multi-core environment. ISVs such as Oracle, Microsoft, SAP, VMware have made their applications multi-core friendly, giving you more for less.

 

 

 

Another area that you MUST consider is Virtualization or Server Consolidation - where multi-core servers have been known to provide the optimum use of compute resources in your environment. You can read Virtualization benefits in blogs from Sudip Chahal, dave_hill, RK_Hiremane, and K_Lloyd

 

 

 

 

To summarize, enterprise applications running on the 6-core Intel Xeon 7400 processor-based servers will see performance scaling as the number of cores increase. And it WILL get better over time. I hope you have enjoyed reading this. Let me know what you think.

 

 

0 Comments Permalink
0

A 45nm 6-core QnA

Posted by Chris P_Intel Oct 3, 2008

Following my earlier blog, I promised to share answers to some of the more common questions I get from customers on 45nm and mostly about the newest product we have on 6-core 45nm: the Xeon processor 7400 series.

 

1. What does 45nm really mean? A nanometer represents a distance that is one billionth of a meter in length. 45nm represents the width of a single transistor and is used to describe the manufacturing technology Intel uses to create our latest generation of processors. Because of the small 45nm transistor size, Intel is able fit 2 million transistors on the period at the end of this sentence.

 

2. Are all 45nm transistors the same? No. Materials used in silicon manufacturing process can vary from manufacturer to manufacturer. Intel switched over to a high-k dielectric material (Halfnium) that helps dramatically reduce leakage current – improving the performance/watt characteristic of our processors.

 

3. What OEM products feature 6-core 45nm products? Servers based on the processor are expected to be announced from over 50 system manufacturers around the world, including four-socket rack servers from Dell, Fujitsu, Fujitsu-Siemens, Hitachi, HP, IBM, NEC, Sun, Supermicro and Unisys. There are four-socket blade servers from Egenera, HP, Sun and NEC and there are server designs that scale up to 16-sockets from IBM, NEC and Unisys.

 

4. How does 6-core affect my software licensing? Just like with other multi-core processors, licensing will depend on the software vendor. With quad-core most ISVs elected to license by socket or processor meaning that the performance enhancements came “for free” as the number of cores are increased. Recently VMware updated their definition of a “processor” to include up to 6-cores per processor (learn more) meaning that with VMware ESX 3.5 update 2 and Intel Xeon processor 7400 series, IT can deploy a higher density of virtual machines per server without an incremental increase in licensing costs. Everyone does it differently – so do your homework.

 

Other common questions circle around IT usage trends and how this technology can really be applied. Here is an interesting (and somewhat long) video where Intel VP and CIO Diane Bryant discusses with executives from Yahoo, Oracle, MySpace and Verisign about the challenges they face and how technology is helping them. If you choose to listen you will find answers to questions (paraphrased) like?

 

  • What are some of the top challenges IT faces today? How can technology help?

  • Is 6 core performance too much? Does IT have the ability inside their environment to take advantage of this additional compute capacity?

  • Is the software ecosystem is ready for multi-core? Can today's applications take advantage of it?

  • How are customers using Virtualization today and how do they see it changing over time?

  • When virtualizing ... how does IT view MP servers (4 socket) vs DP (2 socket)?

  • When deploying next generation technology, how important is the power capacity of the IT environment when selecting technology?

  • Are Intel Xeon servers powerful and reliable enough to consider moving away from RISC or other proprietary architectures?

 

If I missed your burning question, just ask … I’d be happy to share. Chris

0 Comments Permalink
0

In my last I/O Virtualization blog, earlier this year, I discussed a fundamental problem with virtualizing I/O and one the solution that Intel and VMware have teamed up to deliver - VMDq and VMware NetQueue. These queuing technologies together can help to offload some of the virtual switching (vswitch) functionality to the network adapter from the hypervisor. VMDq provides a method for the Hypervisor to do less work, and also provides a way to share the I/O processing across multiple cores; improving system bandwidth and more fully utilizing its processing power.

 

Now, VMDq and NetQueue are a great solution together that scale well, support Vmotion, and are relatively simple to manage. However, is there a way to get even better performance from your Virtualized I/O?

 

What if there was a way to completely cut the Hypervisor software switch out of the picture and remove the associated latency and CPU overhead? The ideal scenario for optimum performance is for the VM to communicate directly with LAN hardware itself, and bypass the vswitch completely. For example, you could have a single 10 Gigabit port expose multiple LAN interfaces at the hardware level (on the PCI-e bus), and each VM could be assigned directly to a hardware interface. Alternatively, you have multiple physical NICs in the system that could be directly assigned to a given VM. Below is a diagram that summarizes the 3 main variations of attachment for I/O in a virtualized server. Below we will get into more detail to put the diagram in context.

 

 

 

 

In the diagram above, the left side represents an implementation of a virtualized environment with a standard I/O setup using the Hypervisor vswitch and VMDq for I/O performance enhancement. In the middle is an example of direct I/O assignment between a single physical LAN interface and a single Virtual Machine. The implementation on the right is showing what is possible with a single NIC that supports SR-IOV (we'll discuss this later) for a fuller, hardware level I/O virtualization. After taking a moment to understand the basic differences in these three implementations, there are immediately a few obvious benefits here for bypassing the Hypervisor vswitch and going with either of the two directly assigned designs...

 

 

By allowing the Virtual Machines to talk directly to the networking hardware, throughput, latency, and CPU utilization of the I/O traffic processing will be greatly improved. So the question is, "why hasn't this been done before?" Well, the answer is that there are several gotchas to make this implementation work well...

 

 

First, in order to implement this properly, the LAN hardware needs to support some physical capabilities to successfully route the networking traffic in this kind of virtualized system. In addition to all of the above the actual server hardware itself must also support VT-d so that the memory mapping between the Virtual Machine PCI-e memory space and the systems physical memory space are correlated correctly. Also, the actual system itself must also support VT-d so that the memory mapping between the Virtual Machine (I/O data memory address) and the systems physical memory address are correlated correctly.

 

 

Finally, and this is a big one, this kind of implementation while very good for performance just happens to break the ability to move a VM from one physical server to another (VMware Vmotion). This is one of the more widely used aspects of VMware's software that has been utilized heavily by most IT shops. Seamless vmotion support is critical for making any I/O performance improvement deployable in the real world.

 

 

Now, if you stop at the 2nd diagram, and use separate NICs for each VM, you will also miss out on a few key advantages of new Ethernet capabilities. You won't be able to allocate your overall bandwidth between your VMs (each VM will get a single Gig or 10Gig port), and more importantly, you won't be able to effectively share higher bandwidth pipes. For example, a server with a few 10 Gigabit ports may have enough I/O horse power to handle traffic for 30 VMs, but there would be no way to assign only a portion of the bandwidth of the pipe to an individual VM.

 

 

Additionally, the LAN hardware needs to support the ability for each virtual function of the LAN device to be able to support bandwidth segregation (think QoS per VM) and the ability to support multiple queues and traffic classes per LAN virtual function. This last piece is necessary for those who remember the discussion on Fiber Channel over Ethernet (FCoE), as the ability to support multiple traffic classes, and dedicated bandwidth links, are key needs for the storage over Ethernet market.

 

 

Now that I've set up what is needed to make this directly assigned virtualized I/O environment work, and called out the potential problems, you don't need to worry; I won't throw cold water on this idea. In fact, most of the pieces are in place today and there is already work being done to complete the solution as we speak.

 

 

First, Intel network adapters now support some fancy hardware capabilities related to virtualization. In addition to all the hooks for VMDq, our newest NICs support PCI-SIG SR-IOV (I know... technologist love acronyms) which provides the ability to virtualize the LAN at the lowest hardware level. The networking hardware also supports some smart logic to be able to function properly in a virtualized system. For example, VM to VM communication in the same server must be looped back before it gets to the wire or the switch connected to the machine won't know how to route the packet. This is all taken care of in the LAN hardware. And of course, all the support for bandwidth segregation, and support for multiple queues and traffic classes is there as well to make sure Storage and other QoS sensitive applications are still going to work well.

 

 

As for VT-d support, Intel platforms now come with this basically standard, so there is no issue there. But the last most important piece is the ability for an individual VM to be moved between physical servers while still being able to ‘renegotiate' with its physical network connection. The ability to do this is under development by Intel, VMware and others in the industry, and the end goal is to have an architectural framework in place to make this kind of handoff seamless from a hardware and software perspective.

 

 

This architectural framework will be the topic of a future post, as I think I've used up all the lines I can before I start putting my readers to sleep. Until next time!

 

 

Ben Hacker

 

 

0 Comments Permalink
0

At Oracle OpenWorld in the Dell booth on September 22nd – 24th, we educated a large number of IT managers and Oracle Database Administrators about how best to harness the power of the new Xeon 7400 processor for their Oracle Middleware and Database environments. Check out this video and learn about the Xeon 7400 based Dell PowerEdge R900, the features / benefits of this new platform, the virtualization performance advantages, and the energy efficiency benefits of Intel’s 45nm manufacturing process.

 

 

0 Comments Permalink

Filter Blog

By author: By date: By tag: