<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Hyper-V &#8211; Reducing the cost of your BizTalk 2009 farm &#8211; really?</title>
	<atom:link href="http://www.u-g-h.com/2008/12/18/hyper-v-reducing-the-cost-of-your-biztalk-2009-farm-really/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.u-g-h.com/2008/12/18/hyper-v-reducing-the-cost-of-your-biztalk-2009-farm-really/</link>
	<description>Distracting the Mind with Information Overload</description>
	<lastBuildDate>Mon, 16 Jan 2012 21:10:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Owen</title>
		<link>http://www.u-g-h.com/2008/12/18/hyper-v-reducing-the-cost-of-your-biztalk-2009-farm-really/comment-page-1/#comment-74400</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Tue, 14 Apr 2009 09:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.u-g-h.com/?p=2795#comment-74400</guid>
		<description>@Mick: Thanks for your comment. I guess it&#039;s all about giving users options around how their deploy their architecture.</description>
		<content:encoded><![CDATA[<p>@Mick: Thanks for your comment. I guess it&#8217;s all about giving users options around how their deploy their architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mick</title>
		<link>http://www.u-g-h.com/2008/12/18/hyper-v-reducing-the-cost-of-your-biztalk-2009-farm-really/comment-page-1/#comment-74376</link>
		<dc:creator>Mick</dc:creator>
		<pubDate>Mon, 13 Apr 2009 12:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.u-g-h.com/?p=2795#comment-74376</guid>
		<description>Owen - I hear you.
Let me put it in some context.

Virtualisation - you can slice and dice your cores, RAM + disk allocated to each VM.

BTS09 running on W2K8 Hyper-V performs on &#039;average&#039; between 80-95% (MS findings :) of the physical h/w underneath. Which is not bad at all.

For e.g. A client needs to implement a BTS farm (redundancy is important) so they&#039;re up for at least 2 ent. lic. using the traditional method - when given they are just breaking into the bts world.

&quot;Show me it working...&quot; is their current mindset. 

Getting 1 ent. lic. and being able to spin up unlimited bts VMs on the one physical machine - makes perfect sense for them...for now. At a later date - they have all the bts infrastructure to spin up a new box, and move a bts vm over there (thus incurring an additional license cost then, not now)

Given you can get h/w redundancy built into many boxes these days (e.g. psu, nics, RAM etc) a &#039;failure&#039; isn&#039;t as bad as it was.

Going many core cpus (in my experience) has outperformed many cpus fewer cores.

So from a MS perspective (I can see what they&#039;re trying to do), they reduce the price tag of BTS while giving you much of the same functionality &#039;virtually&#039; - easing the USD$40K price tag.

Note: From the field - it&#039;s OK to virtual bts, but not too performant to virtualise SQL.

HTH,

Mick.</description>
		<content:encoded><![CDATA[<p>Owen &#8211; I hear you.<br />
Let me put it in some context.</p>
<p>Virtualisation &#8211; you can slice and dice your cores, RAM + disk allocated to each VM.</p>
<p>BTS09 running on W2K8 Hyper-V performs on &#8216;average&#8217; between 80-95% (MS findings <img src='http://www.u-g-h.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  of the physical h/w underneath. Which is not bad at all.</p>
<p>For e.g. A client needs to implement a BTS farm (redundancy is important) so they&#8217;re up for at least 2 ent. lic. using the traditional method &#8211; when given they are just breaking into the bts world.</p>
<p>&#8220;Show me it working&#8230;&#8221; is their current mindset. </p>
<p>Getting 1 ent. lic. and being able to spin up unlimited bts VMs on the one physical machine &#8211; makes perfect sense for them&#8230;for now. At a later date &#8211; they have all the bts infrastructure to spin up a new box, and move a bts vm over there (thus incurring an additional license cost then, not now)</p>
<p>Given you can get h/w redundancy built into many boxes these days (e.g. psu, nics, RAM etc) a &#8216;failure&#8217; isn&#8217;t as bad as it was.</p>
<p>Going many core cpus (in my experience) has outperformed many cpus fewer cores.</p>
<p>So from a MS perspective (I can see what they&#8217;re trying to do), they reduce the price tag of BTS while giving you much of the same functionality &#8216;virtually&#8217; &#8211; easing the USD$40K price tag.</p>
<p>Note: From the field &#8211; it&#8217;s OK to virtual bts, but not too performant to virtualise SQL.</p>
<p>HTH,</p>
<p>Mick.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

