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

Review wtperf stress_checkpoint_rate option

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT2.3.0
    • Component/s: None
    • Labels:

      Description

      It's not consistent with other checkpoint options in

       

      . Sue points out:

      • Instead of adding another config option, could we just run the already-existing checkpoint_worker thread/code during populate as well?
      • Additionally, that code currently runs on a timer interval rather than number of operations. We could add a general checkpoint_rate option. This would be similar to the sample_interval versus sample_rate that we also have, but either phase would use it.
      • If you believe it is worthwhile to have a separate config option as a rate, only for populate, I suggest renaming it to checkpoint_populate_rate so that it sorts next to the other existing checkpoint config strings. Also clarify the existing ones to say they're workload-only related.
      • If you have a wtperf config file that you want to add, we should add another Jenkins job to stress that code regularly.

        Attachments

          Activity

            People

            • Assignee:
              alexander.gorrod Alexander Gorrod
              Reporter:
              alexander.gorrod Alexander Gorrod
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: