[SERVER-2430] Indexed capped collection performance degrades after there are thousands of entries Created: 28/Jan/11 Updated: 29/May/12 Resolved: 02/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Joseph Wang | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
Initially, two capped collections were created to implement "cache" feature. db.createCollection("purchase", {capped:true, size:10000000}) , {background:true}); ) , {background:true}); The lookup query is done via Date now = new Date(); cur = coll.find(dbQuery).addOption( We've three servers, each has 24 CPUs w/ total 48G. We see the query performance seems to degrade after we've thousands of documents. To get thing moving again, we dropped capped collections and recreated them. Now stats whos > db.refinance.stats() , Attaching the cache code |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 02/Sep/11 ] |
|
Note this may have been addressed in 1.8 with better index compaction |
| Comment by Eliot Horowitz (Inactive) [ 06/Mar/11 ] |
|
Can you provide stats when things are not performing well? |
| Comment by Joseph Wang [ 04/Mar/11 ] |
|
any comment? suggestion? |
| Comment by Joseph Wang [ 02/Feb/11 ] |
|
for capped (indexed) collection, what is the performance difference between capping the number of entries vs the size? |