title: MongoDB stress test
body: <p>I'm doing a test for mongodb. 
  The version of mongo is 2.4.9. And in the database I have more than 2.5 Millions of documents inserted in a collection like:</p>
  
  <pre><code>[{"_id": _id, "id" : _id, "row1": "0000-000000000-000000000-00", "meta" : "domainName", "type" : "domainType", "timestamp" : "01234646458", "relations" : { "direct" [], "indirect": ["domain1", "domain2"]}, "extension" : "net", "usage" : "intranet","extraValue":Math.random()}, ...]
  </code></pre>
  
  <p>The collection just now is indexed, and working good inserting the data, the problem occurs when I'm trying to randomly read the data from the database, with aprox. 100 threads searching a non-specific document each 2 seconds (Each 2 seconds a new operation starts). The operation is simple, is read a document and insert a new document linked (only by reference) with other document, the operations doesn't affect the randomically search. The first 255 minutes, work good, but after 25 minutes the connections are closed  or refushed. The cpu usage is normal and the network usage is normal too, with other database I didn't have the same problem. Exist some consideration in the moment to read data from mongo? Or maybe could be problem of the driver? Just now, the test is with node.js and mongo with the mongodb MongoClient driver.</p>