Changing zstdCompressionLevel does not affect storageSize

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Minor - P4
    • None
    • Affects Version/s: 5.0.3
    • Component/s: None
    • 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
              Reporter:
              Platon workaccount
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: