[SERVER-61248] Validate behaviour of stripping debug info from plan cache entries Created: 04/Nov/21 Updated: 29/Oct/23 Resolved: 21/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Anton Korshunov | Assignee: | Alexander Ignatyev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QO 2021-12-13, QO 2021-12-27, QO 2022-01-10, QO 2022-02-07, QO 2022-02-21, QO 2022-03-07 | ||||||||
| Participants: | |||||||||
| Description |
|
The SBE and classic plan caches use the same serverStatus metric to track the cumulative size. The classic cache uses a special mechanism to reduce memory footprint by stripping debug info from plan cache entries when a certain threshold is reached. We need to make sure that when the threshold is reached by adding entries to the SBE plan cache, the classic cache will start striping debug info even though the size of the classic cache may be below the threshold. |
| Comments |
| Comment by Githook User [ 21/Feb/22 ] |
|
Author: {'name': 'Alexander Ignatyev', 'email': 'alexander.ignatyev@mongodb.com', 'username': 'aligusnet'}Message: |