determine storageEngine specificity in docs
(DOCS-4856)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 9 weeks, 1 day ago |
| Description |
|
the stats information for the new WT output in 3.0 has not been fully updated. Probably want to explain what stats can mean in each engine as well as enumerate the new stats. Some stats such as "mapped" become irrelevant when going from mmap to WT None of the new WT stats are explained and the role compression can play in the existing size stats is not explained. |
| Comments |
| Comment by Kay Kim (Inactive) [ 11/Dec/18 ] |
|
Oops – forgot to close this a while ago |
| Comment by Kay Kim (Inactive) [ 07/Dec/15 ] |
|
part 2 |
| Comment by Githook User [ 29/Oct/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message:
|