determine storageEngine specificity in docs (DOCS-4856)

[DOCS-5642] Cap collection storage size should be described in a context of WT and compression Created: 16/Jun/15  Updated: 23/Aug/17  Resolved: 02/Aug/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: mongodb-3.0
Fix Version/s: None

Type: Sub-task Priority: Major - P3
Reporter: Eitan Klein 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: 8 years, 35 weeks, 1 day ago

 Description   

Cap collection storage size well described well for MMAP, since WT compress the disk size, we should modify the documentation

http://docs.mongodb.org/manual/core/capped-collections/

We might have similar issues with similar vector of problem (size of the disk w/o compression)

see example below.

  "ns" : "sbtest.sbtest",
  "count" : 843881,
  "size" : 999,998,985,
  "avgObjSize" : 1185,
  "storageSize" : 219,582,464,
  "capped" : true,
  "max" : -1,
  "maxSize" : 1,000,000,000,
  "wiredTiger" : {


Generated at Thu Feb 08 07:50:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.