[SERVER-1383] Poor mongoexport performance when using a query Created: 08/Jul/10 Updated: 12/Jul/16 Resolved: 23/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | 1.5.3 |
| Fix Version/s: | 1.7.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Doug Hudson | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Thu Jul 8 18:58:12 db version v1.5.3, pdfile version 4.5 |
||
| Participants: |
| Description |
|
mongoexport is potentially very slow when passing in a query argument. Below is an example of a shell find() that takes 30ms for 571 result documents, but many minutes when trying to export these documents using mongoexport. If it is known for sure that a collection won't change during an export, can mongoexport be told to be more efficient and less strict when creating the output documents? Possibly it's a simple matter of allowing {$snapshot: false} to be specificed, or maybe there is another reason for the large change in efficiency. Either way, providing a simple query which uses an index such as the example given, is currently an unfeasible way to export collection subsets, and one must rely on other manual means to achieve this.
|
| Comments |
| Comment by auto [ 23/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: don't use snapshot with another query |
| Comment by auto [ 23/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: don't use snapshot with another query |