[SERVER-3903] Optimize pure key/value use cases Created: 19/Sep/11 Updated: 25/Jun/15 Resolved: 25/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Dwight Merriman | Assignee: | Dwight Merriman |
| Resolution: | Won't Fix | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
some optimizations are possible for a pure key/value use case. or likely more than just key/value queries but certain operations only. for example imagine using covered indexes and having no collection at all. some sort of optional auto age out for the use case too would be nice although perhaps orthogonal |
| Comments |
| Comment by Ian Whalen (Inactive) [ 25/Jun/15 ] |
|
I'm closing this as Won't Fix given the current direction and prioritization of MongoDB feature development. |