[DOCS-7942] Comment on: "manual/reference/command/dbStats.txt" Created: 23/May/16  Updated: 09/Aug/16  Resolved: 05/Aug/16

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

Type: Bug Priority: Major - P3
Reporter: Joe Drumgoole (Inactive) Assignee: Jonathan DeStefano
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.com/manual/reference/command/dbStats/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Referrer: https://docs.mongodb.com/manual/reference/method/db.stats/
Screen Resolution: 1920 x 1080


Participants:
Days since reply: 7 years, 27 weeks, 1 day ago
Story Points: 0.25

 Description   

Think the documentation would be clearer if it explained that "storageSize" is the size of the file on disk. dataSize is the size of the uncompressed documents inside the collection. So in many cases dataSize can be larger than storageSize, This is counterintuitive.

An example would help. Here e.g. create a db (db.stats = 0). Insert a single record (db.stats jumped up as storage is allocated). Now remove that record. storageSize is unchanged but dataSize goes back to 0.



 Comments   
Comment by Githook User [ 09/Aug/16 ]

Author:

{u'username': u'jdestefano-mongo', u'name': u'jonathan', u'email': u'jonathan.destefano@10gen.com'}

Message: DOCS-7942 Added statement that dataSize is uncompressed and outlined the differences between MMAPv1 and WiredTiger. - JD

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/664cf846054d91564c4cab880268e9d2be899a45

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