[SERVER-17895] Server should not clear collection plan cache periodically when write operations are issued Created: 06/Apr/15 Updated: 15/Mar/17 Resolved: 23/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.7, 3.1.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||
| Sprint: | Quint Iteration 7 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Each collection's query plan cache for is currently cleared after 1000 write operations are issued against the collection. This gives distribution changes a chance to affect planning decisions for query shapes that are already cached. However, clearing the entire plan cache is aggressive, and at worst will cause deployments with a heavy write load to effectively not use the query plan cache at all. This mechanism will be made obsolete by |
| Comments |
| Comment by Githook User [ 26/Aug/15 ] |
|
Author: {u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}Message: (cherry picked from commit 26c5394f79d12ac1c9df7263199e2926ee2e19ff) Conflicts: |
| Comment by Githook User [ 28/Jul/15 ] |
|
Author: {u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}Message: |
| Comment by Githook User [ 23/Jul/15 ] |
|
Author: {u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}Message: |