title: Application Pool recycling results in very long response times
body: <p>I've read somewhere, that application pool recycling shouldn't be very noticeable to the end user, when overlapping is enabled, but in my case that results in at least 10 times longer responses than usually (depending on load, response time from regular 100ms grows up to 5000ms). Also that is not for a single request, but several ones right after pool recycling (I was using ~10 concurrent connections when testing this).</p>
  
  <p>So questions would be:   </p>
  
  <ol>
  <li>In my opinion I don't do anything, that would take a long time on application start - in general, that is only IoC container and routing initialization, also even I would do something  - that is what overlapping should take care, or not?   </li>
  <li>Is sql connection pool destroyed during pool recycling and could that be a reason for long response times?   </li>
  <li>What would be the best method to profile what is taking so long? Also may be there are ideas, what could take so long from IIS/.NET side, and how to avoid that.</li>
  </ol>