[DOCS-4976] avgObjSize documentation mistake (in one place) Created: 11/Mar/15 Updated: 30/Oct/23 Resolved: 01/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | William Cross | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 7 years, 45 weeks, 5 days ago |
| Description |
|
The collStats command which is also used by db.collection.stats currently claims that avgObjSize is the average Object size; in fact, it's the object size, plus any padding. Please see the attached files, which display avgObjSize for power of 2 sizes allocation, as well as no padding allocation, for two collections with differently-sized documents in them (all of which are identical in size within a given collection). |
| Comments |
| Comment by Githook User [ 01/Apr/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by William Cross [ 18/May/15 ] |
|
We might also want to note that this is somewhat approximate; using power of two sizes allocation, I never quite see the size as being 2^n, but when I look at the data files, it's actually 2^n from the start of one document to the start of the next. |