|
| 1 | +.\" SPDX-License-Identifier: CC-BY-SA-4.0 or-later |
| 2 | +.\" SPDX-FileCopyrightText: 2024 grommunio GmbH |
| 3 | +.TH gromox\-mbsize 8 "" "Gromox" "Gromox admin reference" |
| 4 | +.SH Name |
| 5 | +gromox\-mbsize \(em Mailbox size analysis |
| 6 | +.SH Synopsis |
| 7 | +\fBgromox\-mbsize\fP \fIdirectory\fP |
| 8 | +.SH Description |
| 9 | +Shows a detailed view of how a mailbox size translates to on-disk usage. |
| 10 | +Explanation of the columns/rows follows. |
| 11 | +.PP |
| 12 | +Apparent size: This is the exact size of the object, or simply the sum |
| 13 | +of sizes of objects. |
| 14 | +.PP |
| 15 | +On FS: This is the space that is used on the filesystem, and is subject |
| 16 | +to fs block sizes. Details about this behavior may be found on |
| 17 | +<https://en.wikipedia.org/wiki/Block_(data_storage)>. As a result, |
| 18 | +the on-disk size may be larger than the apparent size. |
| 19 | +.PP |
| 20 | +RFC5322/Mbox: For the sake of IMAP, RFC5322 copies of messages and some |
| 21 | +metadata is retained. |
| 22 | +.PP |
| 23 | +RFC5322 Received: Applies to messages received via delivery(8gx). |
| 24 | +.PP |
| 25 | +RFC5322 Sent: Applies to any other message. |
| 26 | +.PP |
| 27 | +Body analysis: A set of 4 MAPI properties that usually get stored as files on |
| 28 | +disk rather than inside the sqlite database: PR_BODY, PR_HTML, |
| 29 | +PR_RTF_COMPRESSED and PR_INTERNET_TRANSPORT_HEADERS. In gromox\-mbsize, these |
| 30 | +are considered "body". |
| 31 | +.PP |
| 32 | +Attachment analysis: What it says. Not all MIME parts are or stay an |
| 33 | +attachment; for example, calendar items/meeting requests are usually converted |
| 34 | +to MAPI objects. |
| 35 | +.PP |
| 36 | +Missing items/Apparent: The number of MAPI properties/attachments which have a |
| 37 | +dangling reference into the filesystem. |
| 38 | +.PP |
| 39 | +Missing items/FS: The on-disk number of files that seem to be absent. This |
| 40 | +number can be lower than Apparent due to internal data deduplication that is |
| 41 | +transparent to MAPI/exmdb clients. |
| 42 | +.PP |
| 43 | +Informational content: The logical amount of data that is represented by those |
| 44 | +four MAPI properties / by MAPI attachments. |
| 45 | +.PP |
| 46 | +After deduplication: The logical amount of unique bodies/attachments. |
| 47 | +.PP |
| 48 | +Dedup ratio/gains: For the "body" group, there are usually little gains to be |
| 49 | +observed in practice; bodies are just very unique. Messages like "test" are |
| 50 | +ironically the ones that benefit. Attachments dedup a little better, owing to |
| 51 | +many people sending/receiving redundant information, such as company logos. |
| 52 | +.PP |
| 53 | +After compression: Besides deduplication, Gromox can also compress before data |
| 54 | +goes to disk. This is also the final form and so there is an apparent and an |
| 55 | +on-disk value. The on-disk value may be higher due to aforementioned filesystem |
| 56 | +block sizing. |
| 57 | +.PP |
| 58 | +File compress ratio/gains: The earnings going from Dedup to Compressed. |
| 59 | +.PP |
| 60 | +IFC compress ratio/gains: The earnings going from Informational Content to |
| 61 | +Compressed. |
| 62 | +.PP |
| 63 | +MAPI reported sizes: The PR_MESSAGE_SIZE property of a store, folder, message, |
| 64 | +and the PR_ATTACH_SIZE property of an attachment, all give a close |
| 65 | +approximation to the amount of data needed to transfer the object(s) over a |
| 66 | +MAPI connection. |
| 67 | +.PP |
| 68 | +NTS deviation: how much the Network Transfer Size is off from the on-disk size. |
| 69 | +.PP |
| 70 | +Provisioning factor: The ratio between on-disk usage and the logical mailbox |
| 71 | +size reported inside MUAs. |
| 72 | +.SH See also |
| 73 | +\fBgromox\fP(7) |
0 commit comments