[SERVER-11699] Update command: unexpected performance Created: 14/Nov/13 Updated: 10/Dec/14 Resolved: 21/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Write Ops |
| Affects Version/s: | 2.4.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Raul Diaz | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
I have a strange behavior related to the update command. The execution time is quite different if the collection has indexes or not. I have a document like this: , { "a": "2a", "b": "2b" } ] If I execute an update like this (to add a field) in 10000 elements collection: ) It takes: If I create an index on field "array1.a" and repeat the same test, the result is quite different: Why the index is affecting so much? I don't understand why if the index is not defined on that field is affecting in the time execution. Thanks a lot Raul |
| Comments |
| Comment by Asya Kamsky [ 21/Dec/13 ] |
|
duplicate of |