[DOCS-11416] Add documentation for "More efficient updates to large documents in WiredTiger cache" Created: 06/Mar/18 Updated: 06/Dec/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 3.6 Core Server |
| Fix Version/s: | 3.6 Core Server |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James Kovacs | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | storage, wiredtiger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.mongodb.com/manual/core/wiredtiger/ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Story Points: | 0.2 | ||||||||
| Description |
|
WiredTiger uses Multiversion Concurrency Control (MVCC) to maintain multiple views of data for the lifetime of sessions that can read it. WiredTiger’s in-memory (cache) format is different from the on-disk format. In MongoDB 3.6, the cache implementation improves efficiency for small updates to large documents by adding the capability to store deltas rather than copying the full document for each in-memory version required. When flushed to disk, a full version of the document must still be constructed. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |