How can MongoDB dataSize be larger than storageSize?

Question

As far as I understand, the storage size for MongoDB should always be larger than data size. However, after upgrading to Mongo 3.0 and using WiredTiger, I start seeing that

Answer 1

The storageSize metric is equal to the size (in bytes) of all the data extents in the database. Without compression, this number is larger than dataSize because it includes yet-unused space (in data extents) and space vacated by deleted or moved documents within extents. However, as you are using the WiredTiger storage engine, data is compressed on the disk and is therefore smaller than the dataSize.

Answer 2

MongoDB 3.0 with WiredTiger engine uses 'snappy' compression by default. If this affects your DB performance, you can consider to turn it off (blockCompressor: none) in the mongod.conf file:

storage:
  engine: wiredTiger
  wiredTiger:
    collectionConfig:
      blockCompressor: none