<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malaysia VMware Communities &#187; Processors</title>
	<atom:link href="http://malaysiavm.com/blog/tag/processors/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Nehalem heated up the Virtualization</title>
		<link>http://malaysiavm.com/blog/nehalem-heated-up-the-virtualization/</link>
		<comments>http://malaysiavm.com/blog/nehalem-heated-up-the-virtualization/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 15:40:02 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[Nehalem]]></category>
		<category><![CDATA[Processors]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=1187</guid>
		<description><![CDATA[As we noticed that all servers vendors like HP, DELL and IBM  had launched their latest generation of servers to support the Intel Nehalem which also name as Intel Xeon 5500 series high performing virtualization chipset. I had read up couples of review from the expert which provide some useful information for reference purpose. VMETC [...]]]></description>
			<content:encoded><![CDATA[<p>As we noticed that all servers vendors like HP, DELL and IBM  had launched their latest generation of servers to support the Intel Nehalem which also name as Intel Xeon 5500 series high performing virtualization chipset. I had read up couples of review from the expert which provide some useful information for reference purpose.</p>
<p><a href="http://vmetc.com/2009/04/06/intel-nehalem-processor-is-big-news-for-virtualization/">VMETC</a></p>
<p><a href="http://virtualizationreview.com/blogs/weblog.aspx?blog=3740&amp;rss=1">Virtualization Review</a></p>
<p><span id="more-1187"></span>Both articles talk a little bit Nehalem. Personally, I will be very excited to take a test on this and perform the test comparison within the current quad core. VMETC did mention as it will able to support up to 21 VMs per core, and this is a real amazing number to be achieved.  Nehalem quad core will able to replace 9 single core xeon processors with 20 % energy saving.  This will boost up the CPU performance and reduce the power consumption.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/nehalem-heated-up-the-virtualization/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Maximum numbers of Vcpu in single ESX Host</title>
		<link>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/</link>
		<comments>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/#comments</comments>
		<pubDate>Sat, 28 Feb 2009 06:23:55 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Server]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[Processors]]></category>
		<category><![CDATA[vcpu]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=916</guid>
		<description><![CDATA[If we refer to the current version which is ESX 3.5 u3, the maximum number of Vcpu per ESX server is 192 per ESX Servers. Personally, I think the number of Vcpu per ESX servers is too minimal. Imagine if we do run a servers with 4 or 8 physical CPU sockets and we consolidate [...]]]></description>
			<content:encoded><![CDATA[<p>If we refer to the current version which is <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> 3.5 u3, the maximum number of Vcpu per ESX server is 192 per ESX Servers. Personally, I think the number of Vcpu per ESX servers is too minimal. Imagine if we do run a servers with 4 or 8 physical CPU sockets and we consolidate 40 : 1 Physical <a href="http://malaysiavm.com/blog/tag/server">server</a> in our virtualization environment, we will hit to the bottleneck on maximum numbers of Vcpu per ESX servers but not due to the <a href="http://malaysiavm.com/blog/tag/cpu">CPU</a> consumption.I hope VMWare should revise the configuration to greater number or 256 Vcpu per ESX servers.</p>
<p><span id="more-916"></span></p>
<p>The reason of virtualizing today, is really not about sacrifice performance. In our environment, we have most VMs running with 4 Vcpu as the result of customer compare VM to Physical Servers to ensure the performance is sustainable or improve when they switch to <a href="http://malaysiavm.com/blog/tag/vm">VM</a>. When the VM itself is idle or less busy, it will not consume too much resources on the Physical CPU cores. Next release of ESX will go for 8Vcpu per VM. The number of Vcpu been assigned to the VMs which require extra <a href="http://malaysiavm.com/blog/tag/cpu">CPU</a> resources will increase too.</p>
<p><strong>Updated:</strong> <a href="http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_config_max.pdf">Configuration Maximums for VMware Infrastructure 3</a> &#8211; Number of Virtual CPU = 192</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/maximum-numbers-of-vcpu-in-single-esx-host/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Fully Utilize the CPUs of ESX host</title>
		<link>http://malaysiavm.com/blog/fully-utilize-on-cpu-for-esx-host/</link>
		<comments>http://malaysiavm.com/blog/fully-utilize-on-cpu-for-esx-host/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 01:17:03 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Data Center]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[Processors]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=800</guid>
		<description><![CDATA[Been a while we all working on virtualization for consolidation purpose, I am sure that 1 of the biggest selling point we always remind the customers and management is we will able to fully utilize the investment we put in for the servers in our data center with virtualization in place. Most of the time, [...]]]></description>
			<content:encoded><![CDATA[<p>Been a while we all working on virtualization for consolidation purpose, I am sure that 1 of the biggest selling point we always remind the customers and management is we will able to fully utilize the investment we put in for the servers in our data center with <a href="http://malaysiavm.com/blog/tag/virtualization">virtualization</a> in place. Most of the time, we may still not 100% utilize the servers capacity due to some consideration of High Availability and Performance issues.</p>
<p>Here I am interesting to show 1 of the screen shot I capture during my stress test on the <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> host for our production machine which hit to 100% of the CPU  utilization on the ESX host level.</p>
<p><a href="http://malaysiavm.com/images/fullyutilize.jpg" rel="shadowbox[sbpost-800];player=img;"><img src="http://malaysiavm.com/images/fullyutilize.jpg" alt="null" width="503" height="120" /></a></p>
<p>Click the picture above for full view</p>
<p><span id="more-800"></span></p>
<p>This will be really amazing if we can keep this kind of utilization without impact to the performance for the <a href="http://malaysiavm.com/blog/tag/vm">VM</a> guests. Unfortunately, it does slow down the VM guests in my case as many of us know that we shouldn&#8217;t keep the ESX servers resource utilization actively more than 90%. In this round of test, I manage to achieve 40 : 1 ESX host consolidation at my ESX Servers. The normal day, we will always have 28 : 1 as minimal.</p>
<p>Price cut from Intel and 6 cores <a href="http://malaysiavm.com/blog/tag/cpu">cpu</a> will definately increase the consolidation ratio in our case moving forward. The integration with the latest technology and <a href="http://malaysiavm.com/blog/tag/esx4">ESX 4</a> will really help in the case to achieve higher number consolidation ratio moving forward.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/fully-utilize-on-cpu-for-esx-host/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Intel Slash the Processors Price</title>
		<link>http://malaysiavm.com/blog/intel-slash-the-processors-price/</link>
		<comments>http://malaysiavm.com/blog/intel-slash-the-processors-price/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 00:59:59 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Industry News]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[Processors]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=796</guid>
		<description><![CDATA[According to the source from Informationweek.com, Intel had confirmed with the price slash for the quad core XEON processors and Desktop Processors too. For more information, please refer to the link below Information Week &#8211; Intel slash processor price In this economy situation, this is really helpful. For my personal experience, we always experience price [...]]]></description>
			<content:encoded><![CDATA[<p>According to the source from Informationweek.com, <a href="http://malaysiavm.com/blog/tag/intel">Intel</a> had confirmed with the price slash for the <a href="http://malaysiavm.com/blog/tag/quad">quad</a> core <a href="http://malaysiavm.com/blog/tag/xeon">XEON</a> processors and Desktop Processors too. For more information, please refer to the link below</p>
<p><a href="http://www.informationweek.com/news/hardware/processors/showArticle.jhtml?articleID=212901475">Information Week &#8211; Intel slash processor price</a><br />
<span id="more-796"></span><br />
In this economy situation, this is really helpful. For my personal experience, we always experience price increase significantly when we choose the upgrade of <a href="http://malaysiavm.com/blog/tag/processor">processor</a> spec from 2.6Ghz to 3.0Ghz. The new pricing will allow the vendor to revise their current servers pricing and helpful for us who need powerful chips to support the <a href="http://malaysiavm.com/blog/tag/virtualization">virtualization</a> environment. I am really waiting the price cuts from the vendor in my negotiation for my additional <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> servers that I plan.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/intel-slash-the-processors-price/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>6 cores and 8 cores CPU licensing module for VMware</title>
		<link>http://malaysiavm.com/blog/6-cores-and-8-cores-cpu-licensing-module-for-vmware/</link>
		<comments>http://malaysiavm.com/blog/6-cores-and-8-cores-cpu-licensing-module-for-vmware/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 17:04:15 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Industry News]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[Hyper-V]]></category>
		<category><![CDATA[License]]></category>
		<category><![CDATA[Processors]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Xen]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=79</guid>
		<description><![CDATA[As 6 cores and 8 cores per cpu is going to be launched in the market, there had been some discussion going on about the licensing model current apply to the VMware licensing policies. As current agreement, it will maximum allow 4 cores per CPU sockets. Down the road, it will be 6 cores and [...]]]></description>
			<content:encoded><![CDATA[<p>As 6 cores and 8 cores per cpu is going to be launched in the market, there had been some discussion going on about the licensing model current apply to the <a href="http://malaysiavm.com/blog/tag/vmware/">VMware</a> licensing policies. As current agreement, it will maximum allow 4 cores per CPU sockets. Down the road, it will be 6 cores and 8 cores per CPU. They might be a chances of <a href="http://malaysiavm.com/blog/tag/vmware/">VMware</a> to change their CPU licensing model in the future, or they may stick with the current policy which base on the physical CPU sockets. <a href="http://malaysiavm.com/blog/tag/vmware/">VMware</a> is the best products at the current Virtualization market, but they do need to understand that the TCO for a users to start the Virtual Infrastructure Enterprise is more or double the price of the potential customer to switch for Xen, Citrix or Hyper-V. Personally, </p>
<p><span id="more-79"></span></p>
<p>I do hope the Licensing Module will be remain and <a href="http://malaysiavm.com/blog/tag/vmware/">VMware</a> may need to consider to reduce the licensing or provide additional software or services to be bundle together. Let&#8217;s keep an eye on this and soon will have some announcement on this by VMware.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/6-cores-and-8-cores-cpu-licensing-module-for-vmware/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.401 seconds -->

