title: How efficient can Meteor be while sharing a huge collection among many clients?
body: <p>Imagine the following case:</p>
  
  <ul>
  <li><p>1,000 clients are connected to a Meteor page displaying the content of the "Somestuff" collection.</p></li>
  <li><p>"Somestuff" is a collection holding 1,000 items.</p></li>
  <li><p>Someone inserts a new item into the "Somestuff" collection</p></li>
  </ul>
  
  <p>What will happen:</p>
  
  <ul>
  <li>All <code>Meteor.Collection</code>s on clients will be updated i.e. the insertion forwarded to all of them (which means one insertion message sent to 1,000 clients)</li>
  </ul>
  
  <p>What is the cost in term of CPU for the server to determine which client needs to be updated?</p>
  
  <p>Is it accurate that only the inserted value will be forwarded to the clients, and not the whole list?</p>
  
  <p>How does this work in real life? Are there any benchmarks or experiments of such scale available?</p>