This would help users understand when increasing memory consumption is due to growing plan cache entries. Right now, users have no insight into what portion of heap memory outside the WiredTiger cache is being used for the plan cache.
This may be difficult to implement without SERVER-40360, which would change the architecture so that there is a single plan cache per mongod rather than a plan cache per collection.
- is related to
-
SERVER-34886 Plan cache size is bounded by number of entries rather than memory footprint
-
- Backlog
-
-
-
- Backlog
-
-
-
- Closed
-