Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6132

Investigate reasons for bigger _id index after durable history drop

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      mark.callaghan reported in a HELP ticket this issue. Even though we are looking at data size issues through WT-6082, I am creating a ticket to MongoDB _id index issues. This might end up as a dup of another ticket eventually.

      Mark says:

      Updates with results for 4.4 prior to durable history merge. _id index is larger in 4.4 before and after durable history merge but the size is worse after the merge

      4.4pre is:

      {"mongodVersion_vii":"db version v4.3.4-125-g83aa04c"} {"gitVersion":"83aa04c..."}

      Update - the columns below had the wrong lablels

      440rc1 == 4.4.0-rc1
      
      44pre is:
      {"mongodVersion_vii":"db version v4.3.4-125-g83aa04c"}
      {"gitVersion":"83aa04c..."}
      
      
      size in GB for 100M docs like { _id: $int, a: $int }
                      440rc1  44pre   4.2.5
      collection      4.9     3.6     3.5
      _id index       3.1     1.4     1.2
      "a" index       1.1     1.1     1.1
                      ---     ---     ---
      total           9.1     6.1     5.8
      
      bytes/thing : thing is doc or index entry
                      440rc1  44pre   4.2.5
      collection      52.6    38.7    37.6
      _id index       33.3    15.0    12.9
      "a" index       11.8    11.8    11.8
                      ----    ----    ----
      total           97.7    65.5    62.3
      

            Assignee:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: