Databases
StackOverflow2013
Postsdbo
POMongoDB querying performance for over 5 million records
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMongoDB querying performance for over 5 million records
    primarykey
    data
    text
    <p>We've recently hit the >2 Million records for one of our main collections and now we started to suffer for major performance issues on that collection.</p> <p>They documents in the collection have about 8 fields which you can filter by using UI and the results are supposed to sorted by a timestamp field the record was processed.</p> <p>I've added several compound indexes with the filtered fields and the timetamp e.g:</p> <pre><code>db.events.ensureIndex({somefield: 1, timestamp:-1}) </code></pre> <p>I've also added couple of indexes for using several filters at once to hopefully achieve better performance. But some filters still take awfully long time to perform.</p> <p>I've made sure that using explain that the queries do use the indexes I've created but performance is still not good enough.</p> <p>I was wondering if sharding is the way to go now.. but we will soon start to have about 1 million new records per day in that collection.. so I'm not sure if it will scale well..</p> <p>EDIT: example for a query:</p> <pre><code>&gt; db.audit.find({'userAgent.deviceType': 'MOBILE', 'user.userName': {$in: ['nickey@acme.com']}}).sort({timestamp: -1}).limit(25).explain() { "cursor" : "BtreeCursor user.userName_1_timestamp_-1", "isMultiKey" : false, "n" : 0, "nscannedObjects" : 30060, "nscanned" : 30060, "nscannedObjectsAllPlans" : 120241, "nscannedAllPlans" : 120241, "scanAndOrder" : false, "indexOnly" : false, "nYields" : 1, "nChunkSkips" : 0, "millis" : 26495, "indexBounds" : { "user.userName" : [ [ "nickey@acme.com", "nickey@acme.com" ] ], "timestamp" : [ [ { "$maxElement" : 1 }, { "$minElement" : 1 } ] ] }, "server" : "yarin:27017" } </code></pre> <p>please note that deviceType has only 2 values in my collection.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USYarin Miran
    1. USYarin Miran
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMongoDB querying performance for over 5 million records
      1. USOkky
      1. VTFavorite
    2. VO
      singulars
      1. POMongoDB querying performance for over 5 million records
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMongoDB querying performance for over 5 million records
      1. USanvarik
      1. VTFavorite
    1. COAre you using the `limit` argument?
      singulars
      1. POMongoDB querying performance for over 5 million records
      1. USJoe
    2. COnice one! I will probably have the similar scenario in future and answers might be helpful to me as well. How big is your database having that collection? How long did it take before querying those 8 KV pairs before you reach 2mil and how long is it taking now? (just curious)
      singulars
      1. POMongoDB querying performance for over 5 million records
      1. USanvarik
    3. COJoe, yes ofcourse I'm using limits, at the moment I'm limiting my results to 25 documents. I'm not even wanna talk about skips since I'm gonna replace them with range queries in the near future.
      singulars
      1. POMongoDB querying performance for over 5 million records
      1. USYarin Miran
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload