title: Azure Web Job - Performance impact of multiple functions in the same web job and/or multiple web jobs in the same web app?
body: <p>There are 3 ways to deploy a new function via web job:</p>
  
  <ol>
  <li>Create a new web app, and deploy a web job with the function in it.</li>
  <li>Add a new function to an existing web job (so now you have multiple functions in one web job).</li>
  <li>Add a new web job to a web app (so now you have multiple web jobs in the same web app).</li>
  </ol>
  
  <p>All web jobs and web job functions that are on the same web app are hosted on the same VM, so maybe the material impact of all 3 is the same. But I wonder what is the difference.</p>
  
  <p>What guidance is there for deciding how I should add a new web job function to my cloud solution?</p>
  
  <ol>
  <li>New web app with web job</li>
  <li>or new web job in an existing web app with other web jobs</li>
  <li>or a new function in an existing web job with other functions.</li>
  </ol>
  
  <p>I'm interested in how it works, guidance, best practices, and performance impact of these 3 options.</p>