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

Separate System Performance workloads into tasks containing logical groupings

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0-rc3
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      QuInt B (11/02/15), QuInt C (11/23/15)

      Description

      proposed breakdown is to take the single_cluster_test and break it into the following tasks:

      • YCSB_WT
        • ycsb_load
        • ycsb_100read
        • ycsb_50read50update
      • YCSB_MMAPv1
        • ycsb-mmapv1_load
        • ycsb-mmapv1_100read
        • ycsb-mmapv1_50read50update
      • custom_workloads_WT
        • contended_update-wiredTiger
        • map_reduce_1M_doc-wiredTiger
      • customer_workloads_MMAPv1
        • contended_update-mmapv1
        • map_reduce_1M_doc-mmapv1

      And then breaking down shard_shard_cluster_test as follows:

      • YCSB_WT
        • ycsb_load
        • ycsb_100read
        • ycsb_50read50update
      • YCSB_MMAPv1
        • ycsb-mmap_load
        • ycsb-mmap_100read
        • ycsb-mmap_50read50update
      • customer_workloads_MMAPv1
        • map_reduce_1M_doc-mmapv1
      • customer_workloads_WT
        • map_reduce_1M_doc-wiredTiger

      But note the emphasis on "proposed". It would be good to list here a few of the additional tests that are incoming in order to 'future-proof' our information architecture.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: