[DOCS-3198] Improve documentation on ordered bulk operations for 2.6 Created: 17/Apr/14 Updated: 16/Mar/15 Resolved: 27/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.6 |
| Fix Version/s: | v1.3.7, mongodb-2.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 33 weeks, 5 days ago |
| Description |
|
The documentation on the new initializeOrderedBulkOp command needs some further detail on how the bulk operations are actually processed. In particular, "ordered" operations have a performance impact depending on how the operations are interleaved (consecutive operations that are the same can be be more effectively batched). A few blog posts go into more helpful detail:
|
| Comments |
| Comment by Githook User [ 27/Jun/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |