[SERVER-13325] Allow page fault of updated indexes to happen outside of locks Created: 24/Mar/14 Updated: 06/Dec/22 Resolved: 01/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Write Ops |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Currently updates do not try to ensure that any updated indexes, or more specifically the parts we need to write to, are in memory before writing the update. With the change of not using PageFaultExceptions there is no longer a way to communicate this information up or down the layers to handle page faults from index pages. While some of the indexes could be covered by the query side, that can only include the indexes being used by the query system. |