[SERVER-40764] Add LRU cache to ESE v1 keystore Created: 22/Apr/19 Updated: 07/May/19 Resolved: 07/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jonathan Reams | Assignee: | Jonathan Reams |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Security 2019-05-06, Security 2019-05-20 |
| Participants: |
| Description |
|
As part of the [File System Snapshot of Encrypted Storage Engine|PM-1208] project, decrypting ESE pages my involve looking up keys from previous database key roll overs. If the performance of relying on WT to keep keys cached in memory is not sufficient, we should add an LRU cache to cache them at the ESE keystore layer. |
| Comments |
| Comment by Jonathan Reams [ 07/May/19 ] |
|
Instead of adding a second LRU cache, we decided to rely on wiredtiger's page cache. |