-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
QuInt B (11/02/15), QuInt C (11/23/15)
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.
- is duplicated by
-
-
- Closed
-