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

Run snapshot_reads benchmark with 32/64 tickets and a single FIFO queue

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Execution Team 2022-04-18, Execution Team 2022-05-02

    Description

      In SERVER-65156 we noticed snapshot_reads had some strange behaviour. In the high concurrency cases, snapshot_reads_load_throughput improved considerably when reducing the number of maximum tickets, which was in line with other (write) workloads such as ParallelInsert. However snapshot_reads_with_load regressed a lot.

      This test runs writes in half the threads and snapshot reads in the other half. Our guess is that the reduced number of tickets improved our write throughput, and our improved write throughput could have affected negatively our read throughput, possibly due to WT-9074

      One way to reduce the read threads starvation would be to have them share a single FIFO queue with writes.

      Attachments

        Activity

          People

            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            daniel.gomezferro@mongodb.com Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: