title: Issue with Heroku's production configuration: a set of two dynos takes 8 seconds to respond
body: <p>I have an interrogation regarding Heroku's dynos.</p>
  
  <p>As of now my app runs two 512MB dynos and I was pretty certain that this configuration, i.e. more than one dyno, ensured that the container's application was started and ready to serve clients.</p>
  
  <p>However, I frequently notice that the dynos are not always started and it takes something like 8 seconds to load the app. See screen shot below. The host XXXX.herokuapp.com spends nearly 8 seconds in "waiting".</p>
  
  <p>Has anyone else experienced such issues with Heroku? How can they be resolved?</p>
  
  <p><img src="https://i.stack.imgur.com/5oC2V.jpg" alt="screen shot"></p>