[SERVER-21026] benchRun() should support new "findCmd" operation type Created: 20/Oct/15 Updated: 11/Jan/16 Resolved: 11/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
A new operation type called "findCmd" should be added to benchRun(). This will allow users to specify the raw find command object to use for the query, which will in turn allow users to be able to specify workloads that can't be expressed today (for example: query with a sort using find command). This new operation type will deprecate the existing "find" and "findOne" operation types. Eventually, existing tests should be ported over to use "findCmd", and "find"/"findOne" support should be removed. |
| Comments |
| Comment by David Storch [ 11/Jan/16 ] |
|
Ah ok, in that case I agree that we don't need a special "findCmd" benchRun operation. Closing as Won't Fix per your suggestion. |
| Comment by J Rassi [ 11/Jan/16 ] |
|
david.storch, I suspect this ticket should be closed as "Won't Fix", due to the recent work in benchRun that automatically iterates any cursor returned by a command. Instead of moving query operations over to a new "findCmd" operation type, it seems like instead we should move query operations over to the existing "command" operation type. Do you agree? |