foundationdb/tests/DataDistributionMetrics.txt
Alex Miller 17570b5b10 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 02:03:30 -07:00

25 lines
519 B
Plaintext

testTitle=DataDistributionMetricsCorrectness
testName=DataDistributionMetrics
testDuration=10.0
nodeCount=100000
actorCount=64
keyPrefix=DDMetrics
testName=Cycle
transactionsPerSecond=2500.0
testDuration=10.0
expectedRate=0.025
testName=Mako
testDuration=10.0
transactionsPerSecond=2500
rows=100000
sampleSize=100
valueBytes=16
keyBytes=16
operations=u8i
actorCountPerClient=64
populateData=true
runBenchmark=true
preserveData=false