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

Wired Tiger Compression

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.1
    • Component/s: WiredTiger
    • Environment:
      Amazon Linux
    • ALL

      Hi,

      We recently upgraded out MongoDB from community version 3.4.14 to 4.0.1

      We see that the compression ratio differs for the same type of data between the version

      Hence we did a test and found that compression ratio drastically fell for 3.6+ 

      Version Raw size Storage size Comp Ratio
      4.0 10378066324 1594658816 6.5x
      3.6 10378066324 1599205376 6.49x
      3.4 10378066324 634499072 16.35x

      Can you please suggest if any changes has to be made in the configuration of MongoDB or WiredTiger?

      Below is the wired tiger configuration we are using

      wiredTiger:
      collectionConfig:
      blockCompressor: zlib
      engineConfig:
      directoryForIndexes: true
      journalCompressor: none
      cacheSizeGB: 40
      configString: "eviction_dirty_target=60, eviction_dirty_trigger=80, eviction=(threads_min=20,threads_max=20)"

      Thanks,

      Tanveer

       

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            tanveerm@xilinx.com Tanveer Madan Marate
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: