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

Prune existing tests to stabilize the signal from the change stream perf suite

    • Fully Compatible
    • v7.0, v6.3, v6.0, v5.0, v4.4
    • QE 2023-05-15, QE 2023-05-29
    • 35

      • For the change_stream_latency tests and its derivatives, run only a single configuration: 1KB documents, ~24 worker threads, 1 collection, 1 change stream. Keep the pre-image variants, consider similarly splitting the updateLookup test into its own variant. Consider getting rid of the findOne worker since that just adds load with no direct impact on the test.
      • Consider getting rid of the change_stream_throughput tests entirely. These don't measure anything to do with change streams itself, but instead measure the impact of increasing numbers of change streams on an ongoing read/write workload. One benefit of having these tests around is that they can be correlated against the corresponding change_stream_latency tests; if write throughput improves, change streams latency regresses. But we could get the same information by simply recording write throughput in the change_stream_latency tests.
      • Consider extending the change_stream_listen_throughput test, which is currently insert-only, with mixed-workload, updateLookup and pre-image variants. This doesn't have to happen under this ticket, since it would involve adding new tests rather than reworking the current ones.

      Bernard's comment

            mindaugas.malinauskas@mongodb.com Mindaugas Malinauskas
            sebastien.mendez@mongodb.com Sebastien Mendez
            0 Vote for this issue
            5 Start watching this issue