foundationdb/tests/TPCC.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

20 lines
361 B
Plaintext

testTitle=PopulateTPCCTest
clearAfterTest=false
runConsistencyCheck=false
timeout=3600000
testName=PopulateTPCC
clientsUsed=2
actorsPerClient=1
warehousesPerActor=80
testTitle=TPCCTest
timeout=14400
testName=TPCC
warehousesPerClient=4
testDuration=3600
warmupTime=300
clientsUsed=40
expectedTransactionsPerMinute=1000