Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-60510

Changing zstdCompressionLevel does not affect storageSize

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 5.0.3
    • Component/s: None
    • Labels:
    • ALL
    • Hide

      1. 

      sudo nano /etc/mongod.conf

      storage:
  wiredTiger:
    engineConfig:
      zstdCompressionLevel: 10

      2. DB creation.
      3. 

      use db_name

      4. 

      db.stats()

      storageSize: 9838592

      5. 

      sudo nano /etc/mongod.conf

      storage:
  wiredTiger:
    engineConfig:
      zstdCompressionLevel: 22

      6. Creating DB with the same data.
      7. 

      use db_name

      8. 

      db.stats()

      storageSize: 9838592
      Show
      1. sudo nano /etc/mongod.conf storage: wiredTiger: engineConfig: zstdCompressionLevel: 10 2. DB creation. 3. use db_name 4. db.stats() storageSize: 9838592 5. sudo nano /etc/mongod.conf storage: wiredTiger: engineConfig: zstdCompressionLevel: 22 6. Creating DB with the same data. 7. use db_name 8. db.stats() storageSize: 9838592

      As I understood from the documentation, storageSize depends on compression. But in practice it turned out that changing the compression level does not alter this value. By the way, indexSize slightly varies.

            Assignee:
            yuan.fang@mongodb.com Yuan Fang
            Reporter:
            platon.work@gmail.com Platon workaccount
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: