Azure Service Fabric - Improve Local Performance
<p>When I deploy or exercise the cluster locally, I am facing <strong>drastic recourse degradation</strong> on my local machine.</p>

<p>I wonder if you can recommend a way to mitigate that negative impact (SW &amp; HW)?</p>

<p>Additional info:</p>

<blockquote>
  <p>It is important to understand that the Service Fabric local cluster is
  not an emulator or simulator. It runs the same platform code that is
  found on multi-machine clusters. The only difference is that it runs
  the platform processes that are normally spread across five machines
  on one machine.</p>
</blockquote>

<p><a href="https://azure.microsoft.com/en-us/documentation/articles/service-fabric-get-started-with-a-local-cluster/" rel="nofollow">https://azure.microsoft.com/en-us/documentation/articles/service-fabric-get-started-with-a-local-cluster/</a></p>

<p>One though I had was to add one more SSD, so the OS and Service Fabric will not compete on the bus resource. After adding that SSD and using PowerShell to move the cluster to the new drive (the one without the OS) I can see negligible effect. Looking at the performance monitor, it seems that most of the IO still going to the main (OS) drive. Any thoughts?</p>

<p>I have a standard dev machine with the following specs:</p>

<ul>
<li>Newer i7 CPU</li>
<li>16GB RAM</li>
<li>One SSD  </li>
<li>And a great monitor (just kidding :-)</li>
</ul>

<p>This question might be a good fit for the HW forum as well</p>