title: Is it ok to await a collection of 1000 tasks in a .NET app? Or should batching be used?
body: <p>I have a simple console app testing out some code.</p>
  
  <p>My code has a list of 1000 numbers and putting each number/int onto an Azure Queue. </p>
  
  <p>Now, I do this asyncronously and it's works great. here's my code from my library:</p>
  
  <pre><code>var tasks = stagedFileIds.Select(stagedFileId =&gt; QueueFileToProcessAsync(stagedFileId));
  await Task.WhenAll(tasks)
            .ConfigureAwait(false);
  </code></pre>
  
  <p>Works great.</p>
  
  <p>But .. is this a bad thing? should I batch this into 50's or 25's or something? But most importantly ... batch it?</p>
  
  <p>What is 'the cost' of doing the above code?</p>
  
  <p>Remember, this is a console app <em>right now</em>. I'm going to move this to an Azure Function at some point.</p>