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

Deleting documents takes longer when there are many updates in the history store.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 4.4.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Story Points:
      8
    • Sprint:
      Storage - Ra 2021-05-31, Storage - Ra 2021-06-14

      Description

      I see slower performance when deleting documents after growing the history store. I don't know to what extent this behavior is expected/unexpected.

      This came up in the eMRCf testing described at WT-6776.

      Setup: I start with 1 million smallish (50 - 200 byte) documents in a single collection on a PSA replica set. After creating the documents, I shutdown the secondary. Because I am using the default enableMajorityReadConcern=true, this means that the primary stops advancing the stable timestamp.

      I compare two different scenarios starting from this setup.

      1. Immediately delete 100,000 randomly chosen documents (1/10 of collection)
      2. Perform 8 million updates, 1 million inserts, 1 million deletes, keeping the collection size at 1 million documents, but growing the history store to 3.6 GB. Leave the system idle for 5 minutes so any delayed activity or checkpoints can quiesce. Then delete 100,000 documents at random, as in the first case.

      In both cases Genny reports the latency of each delete operation. In the second case, the deletes take noticeably longer to complete. I'll add the data in a comment.

      Note that this workload is being driven through MongoDB. So each "delete" here is a deleteOne request where we look up a randomly chosen key and delete the oldest document with the key. The collection is indexed on the key field. So the "delete" time here includes the lookup and deleting both the item and the index entries that point to it. And, of course, since the stable timestamp isn't advancing, some (all?) of these deleted values get pushed into the history store.

      I ran these tests with MongoDB 4.4.1.

        Attachments

        1. 4.4.4-rc0.tgz
          9.97 MB
        2. 444rc0_delete.png
          444rc0_delete.png
          58 kB
        3. 444rc0_update.png
          444rc0_update.png
          94 kB
        4. Benchmark timeline.png
          Benchmark timeline.png
          61 kB
        5. comparison.png
          comparison.png
          334 kB
        6. csv.tar.gz
          135.10 MB
        7. declining-delete-performance-low-io.png
          declining-delete-performance-low-io.png
          370 kB
        8. del.png
          del.png
          395 kB
        9. delete.jpg
          delete.jpg
          39 kB
        10. HS Spikes.png
          HS Spikes.png
          51 kB
        11. image-2021-05-24-14-10-03-024.png
          image-2021-05-24-14-10-03-024.png
          149 kB
        12. image-2021-05-24-14-11-07-725.png
          image-2021-05-24-14-11-07-725.png
          195 kB
        13. image-2021-05-24-14-27-05-030.Edit.png
          image-2021-05-24-14-27-05-030.Edit.png
          162 kB
        14. image-2021-05-24-14-27-05-030.png
          image-2021-05-24-14-27-05-030.png
          740 kB
        15. image-2021-05-25-15-33-36-855.png
          image-2021-05-25-15-33-36-855.png
          392 kB
        16. image-2021-05-25-15-35-03-462.png
          image-2021-05-25-15-35-03-462.png
          413 kB
        17. image-2021-05-27-14-38-19-242.png
          image-2021-05-27-14-38-19-242.png
          282 kB
        18. image-2021-05-28-10-55-41-100.png
          image-2021-05-28-10-55-41-100.png
          243 kB
        19. image-2021-05-31-16-27-44-375.png
          image-2021-05-31-16-27-44-375.png
          593 kB
        20. metrics.2020-11-02T15-38-21Z-00000
          7.67 MB
        21. Queuing Delay.png
          Queuing Delay.png
          107 kB
        22. run_with_log.tgz
          10.71 MB
        23. scatter-1.jpg
          scatter-1.jpg
          52 kB
        24. Screen Shot 2020-11-03 at 1.10.35 PM.png
          Screen Shot 2020-11-03 at 1.10.35 PM.png
          39 kB

          Issue Links

            Activity

              People

              Assignee:
              haseeb.bokhari Haseeb Bokhari
              Reporter:
              keith.smith Keith Smith
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: