<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on This Is My Demo</title><link>https://thisismydemo.cloud/tags/performance/</link><description>Recent content in Performance on This Is My Demo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Apr 2026 17:46:25 +0000</lastBuildDate><atom:link href="https://thisismydemo.cloud/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Live Migration Internals and Optimization</title><link>https://thisismydemo.cloud/post/live-migration-internals/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://thisismydemo.cloud/post/live-migration-internals/</guid><description>&lt;p&gt;Live migration is the capability that makes Hyper-V clustering genuinely useful. Without it, maintenance means VM downtime. With it, VMs move between hosts transparently , users don&amp;rsquo;t notice, applications don&amp;rsquo;t interrupt, connections don&amp;rsquo;t drop. But &amp;ldquo;it works&amp;rdquo; isn&amp;rsquo;t enough for production. You need to understand &lt;em&gt;how&lt;/em&gt; it works, what affects performance, and what Windows Server 2025 changed.&lt;/p&gt;
&lt;p&gt;VMware admins know this as vMotion. The Hyper-V equivalent is functionally identical , the VM moves from one host to another while running , but the internal mechanics differ, and the WS2025 improvements are significant.&lt;/p&gt;</description></item></channel></rss>