[SERVER-3564] new $archive update operator to reduce storage waste Created: 09/Aug/11 Updated: 25/Jun/15 Resolved: 25/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Antoine Girbal | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The db tries to understand what padding for a document should be so that it doesnt have to migrate a document too many times. A very easy update operator to add would be $archive and could be use like: )
The application knows exactly when a document is "done" and can call the operator on it. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 25/Jun/15 ] |
|
Given the introduction of the WiredTiger storage engine in 3.0.0 we've seen massive improvements to compression of data on disk, and this particular improvement is no longer necessary. |
| Comment by Derek MacDonald [ 20/Sep/11 ] |
|
For my use case, what Dwight is proposing works perfectly; old documents will not be modified. |
| Comment by Dwight Merriman [ 03/Sep/11 ] |
|
i wonder if we should do this (which requires the developer to do something explicit and learn a new feature), or if the system can be more intelligent and handle this. in theory the database could detect that a document has not changed in a long time, and then do this. we will likely do a background incremental compaction facility anyway; that facility could do that for example. if the documents aren't tiny the 30% will take up disk space but probably not RAM since the pages containing the padding won't be being referenced. |