wbtiger
/
foundationdb
mirror of https://github.com/apple/foundationdb.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
foundationdb/tests/DDMetricsExclude.txt

36 lines
752 B
Plaintext
Raw Normal View History

Make sure only uppercase characters follow underscore in test titles These test titles are used in trace lines, so having an underscore followed by a lower-case character leads to invalid trace lines
2020-11-09 06:23:54 +08:00
testTitle=DDMetricsExclude_Populate
Make the testspec more restrictive in terms of what can be set where. Testspec is currently very permissive in very misleading ways. In particular, the tester parser itself will swallow K=V settings and apply them at the test level, which breaks how a person would expect the scoping to work. Other settings apply to the entire simulation run globally, but appear to be workload specific. Even further, others affect simulation cluster creation or test harness behavior, but can again be set anywhere in a testspec. This changes testspec parsing to error if a setting that applies globally is anywhere but the top of the file, or if a setting that applies test-wide is applied to a workload instead of a test.
2020-07-06 17:03:30 +08:00
testName=Mako
testDuration=30.0
transactionsPerSecond=100000
rows=1000000
sampleSize=100
valueBytes=160
keyBytes=160
operations=i100
actorCountPerClient=128
enableLogging=false
commitGet=false
populateData=true
runBenchmark=true
preserveData=true
added new priority for fetchkeys requests and adjusted ddmetrics workload to run parallel with mako
2019-07-04 02:14:32 +08:00
Make sure only uppercase characters follow underscore in test titles These test titles are used in trace lines, so having an underscore followed by a lower-case character leads to invalid trace lines
2020-11-09 06:23:54 +08:00
testTitle=DDMetricsExclude_Test
Make the testspec more restrictive in terms of what can be set where. Testspec is currently very permissive in very misleading ways. In particular, the tester parser itself will swallow K=V settings and apply them at the test level, which breaks how a person would expect the scoping to work. Other settings apply to the entire simulation run globally, but appear to be workload specific. Even further, others affect simulation cluster creation or test harness behavior, but can again be set anywhere in a testspec. This changes testspec parsing to error if a setting that applies globally is anywhere but the top of the file, or if a setting that applies test-wide is applied to a workload instead of a test.
2020-07-06 17:03:30 +08:00
testName=Mako
testDuration=60.0
transactionsPerSecond=100000
rows=1000000
sampleSize=100
valueBytes=16
keyBytes=16
operations=gr100:100
enableLogging=false
actorCountPerClient=128;
commitGet=false
populateData=false
runBenchmark=true
preserveData=true
added new priority for fetchkeys requests and adjusted ddmetrics workload to run parallel with mako
2019-07-04 02:14:32 +08:00
Make the testspec more restrictive in terms of what can be set where. Testspec is currently very permissive in very misleading ways. In particular, the tester parser itself will swallow K=V settings and apply them at the test level, which breaks how a person would expect the scoping to work. Other settings apply to the entire simulation run globally, but appear to be workload specific. Even further, others affect simulation cluster creation or test harness behavior, but can again be set anywhere in a testspec. This changes testspec parsing to error if a setting that applies globally is anywhere but the top of the file, or if a setting that applies test-wide is applied to a workload instead of a test.
2020-07-06 17:03:30 +08:00
testName=DDMetricsExclude
excludeIp=127.0.0.1
excludePort=4500