title: How to reassign an Application Pool (not Identity) for SharePoint 2013
body: <p><strong>Background</strong>: Our server beyond the recommended limit for SP2013 (<a href="https://technet.microsoft.com/en-us/library/cc262787.aspx#WebserverAppServer]" rel="nofollow noreferrer">Software Boundaries and Limits</a>) on the number of Application Pools per server (10). I'm wondering if that is what is causing a noticeable lag, especially in Central Administration.  I already fixed a time-out issue by <a href="https://sharepoint.stackexchange.com/questions/112358/not-able-to-create-web-application-in-sp-2013/112364#112364">extending the "Shutdown Time Limit"</a> in IIS, but would like also to optimize the performance.</p>
  
  <p><strong>Question</strong>: I'd like several of the SP Web Applications grouped to share an AppPool, so I have 3 AppPools instead more than 10.  By order of preference (1) How do I do this in Central Administration, (2) in PowerShell, (3) or in IIS (most likely not the recommended practice)?  What is the best practice?</p>
  
  <p><strong>Update</strong> (6/29/17): I actually ended up deleted 5 unused Web Apps (7 left, including Central Admin).  That didn't really fix the lag issue on the WFE side, but this these two Powershell commands seem to:  </p>
  
  <pre><code>    PS&gt; Set-SPEnterpriseSearchService -PerformanceLevel PartlyReduced  
      PS&gt; Restart-Service SPSearchHostController
  </code></pre>
  
  <p><em>Credit</em>: <a href="https://sharepoint.stackexchange.com/questions/125174/reduce-noderunner-exe-impact">https://sharepoint.stackexchange.com/questions/125174/reduce-noderunner-exe-impact</a>
  <hr>
  <strong>I still have a lag with making changes in Central Admin.  Still seeking a solution for that.</strong></p>