Figure 11 shows the space savings on the operating system and the extra savings on the PowerStore appliance.

Figure 11.    MongoDB compression and PowerStore data reduction savings different compression algorithms

Blue column: Represents the space reduction on the operating system level

Yellow column: Represents the additional reduction saving on the PowerStore appliance

Without MongoDB compression enabled, the total file system space consumed by all three replica set members would be around 1 TB including the operating system. It is represented as 0% savings on the operating system. However, the actual physical space consumed on the PowerStore appliance is much less than 1 TB. PowerStore alone reduced the total physical space consumption by 34%.

With the snappy compression, which is the default in MongoDB, an 8% reduction is realized on the file system. However, PowerStore provided an additional 30% reduction savings.

Both zlib and zstd compression algorithms do a better job of saving space on the file system with 35% reduction. It is worth noting that even with the more efficient compression algorithms like zstd and zlib, PowerStore can further reduce the total physical space consumption by 11% and 12% respectively.

Note: The amount of reduction varies depending on the type of data.