Typo fix in fix-load documentation

Signed-off-by: Vivek Jha <[email protected]>
duckling69 · May 16, 2024 · 552c3cb · 552c3cb
1 parent c5a569f
commit 552c3cb
Show file tree

Hide file tree

Showing 6 changed files with 21 additions and 21 deletions.
diff --git a/docs/v0.2/Rate_Controllers.md b/docs/v0.2/Rate_Controllers.md
@@ -129,14 +129,14 @@ The linear rate controller can be used in both duration-based and transaction nu
 {
   "type": "linear-rate",
   "opts": {
-    "startingTps": 25,
+    "startTps": 25,
     "finishingTps": 75
     }
 }
 ```
 
 The linear rate controller can be specified by setting the rate controller `type` to the `linear-rate` string. The available options (`opts` property) are the following:
-* `startingTps`: the TPS at the beginning of the round.
+* `startTps`: the TPS at the beginning of the round.
 * `finishingTps`: the TPS at the end of the round.
 
 **Note:** similarly to the [fixed rate controller](#fixed-rate), this controller also divides the workload between the available client, so the specified rates in the configuration are cumulative rates, and not the rates of individual clients. Using the above configuration with 5 clients results in clients that start at 5 TPS and finish at 15 TPS. Together they generate a [25-75] TPS load.

diff --git a/docs/v0.3.2/Rate_Controllers.md b/docs/v0.3.2/Rate_Controllers.md
@@ -54,7 +54,7 @@ The PID rate controller, targeting a backlog of 5 transactions with a starting T
   "type": "fixed-backlog",
   "opts": {
     "unfinished_per_client": 5,
-    "startingTps": 100
+    "startTps": 100
   }
 }
 ```
@@ -128,14 +128,14 @@ The linear rate controller can be used in both duration-based and transaction nu
 {
   "type": "linear-rate",
   "opts": {
-    "startingTps": 25,
+    "startTps": 25,
     "finishingTps": 75
     }
 }
 ```
 
 The linear rate controller can be specified by setting the rate controller `type` to the `linear-rate` string. The available options (`opts` property) are the following:
-* `startingTps`: the TPS at the beginning of the round.
+* `startTps`: the TPS at the beginning of the round.
 * `finishingTps`: the TPS at the end of the round.
 
 **Note:** similarly to the [fixed rate controller](#fixed-rate), this controller also divides the workload between the available client, so the specified rates in the configuration are cumulative rates, and not the rates of individual clients. Using the above configuration with 5 clients results in clients that start at 5 TPS and finish at 15 TPS. Together they generate a [25-75] TPS load.

diff --git a/docs/v0.4.2/Rate_Controllers.md b/docs/v0.4.2/Rate_Controllers.md
@@ -69,7 +69,7 @@ The fixed load rate controller is a controller for driving the tests at a target
 The fixed-load controller can be specified by setting the rate controller `type` to the `fixed-load` string.
 
 Controller options include:
-- `startingTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
+- `startTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
 - `transactionLoad`: the number of transactions being processed by the SUT that is to be maintained
 
 The fixed load controller, aiming to maintain a SUT transaction load of 5, with a starting TPS of 100, is specified through the following controller option:
@@ -79,7 +79,7 @@ The fixed load controller, aiming to maintain a SUT transaction load of 5, with
   "type": "fixed-load",
   "opts": {
     "transactionLoad": 5,
-    "startingTps": 100
+    "startTps": 100
   }
 }
 ```
@@ -126,7 +126,7 @@ The linear rate controller can be used in both duration-based and transaction nu
 The linear rate controller can be specified by setting the rate controller `type` to the `linear-rate` string.
 
 Controller options include:
-- `startingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
+- `startTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
 - `finishingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the end of the round
 
 The following example specifies a rate controller that gradually changes the transaction load from 25 TPS to 75 TPS during the benchmark round.
@@ -135,7 +135,7 @@ The following example specifies a rate controller that gradually changes the tra
 {
   "type": "linear-rate",
   "opts": {
-    "startingTps": 25,
+    "startTps": 25,
     "finishingTps": 75
     }
 }

diff --git a/docs/v0.5.0/Rate_Controllers.md b/docs/v0.5.0/Rate_Controllers.md
@@ -69,7 +69,7 @@ The fixed load rate controller is a controller for driving the tests at a target
 The fixed-load controller can be specified by setting the rate controller `type` to the `fixed-load` string.
 
 Controller options include:
-- `startingTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
+- `startTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
 - `transactionLoad`: the number of transactions being processed by the SUT that is to be maintained
 
 The fixed load controller, aiming to maintain a SUT transaction load of 5, with a starting TPS of 100, is specified through the following controller option:
@@ -79,7 +79,7 @@ The fixed load controller, aiming to maintain a SUT transaction load of 5, with
   "type": "fixed-load",
   "opts": {
     "transactionLoad": 5,
-    "startingTps": 100
+    "startTps": 100
   }
 }
 ```
@@ -126,7 +126,7 @@ The linear rate controller can be used in both duration-based and transaction nu
 The linear rate controller can be specified by setting the rate controller `type` to the `linear-rate` string.
 
 Controller options include:
-- `startingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
+- `startTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
 - `finishingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the end of the round
 
 The following example specifies a rate controller that gradually changes the transaction load from 25 TPS to 75 TPS during the benchmark round.
@@ -135,7 +135,7 @@ The following example specifies a rate controller that gradually changes the tra
 {
   "type": "linear-rate",
   "opts": {
-    "startingTps": 25,
+    "startTps": 25,
     "finishingTps": 75
     }
 }

diff --git a/docs/v0.6.0/Rate_Controllers.md b/docs/v0.6.0/Rate_Controllers.md
@@ -69,7 +69,7 @@ The fixed load rate controller is a controller for driving the tests at a target
 The fixed-load controller can be specified by setting the rate controller `type` to the `fixed-load` string.
 
 Controller options include:
-- `startingTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
+- `startTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
 - `transactionLoad`: the number of transactions being processed by the SUT that is to be maintained
 
 The fixed load controller, aiming to maintain a SUT transaction load of 5, with a starting TPS of 100, is specified through the following controller option:
@@ -79,7 +79,7 @@ The fixed load controller, aiming to maintain a SUT transaction load of 5, with
   "type": "fixed-load",
   "opts": {
     "transactionLoad": 5,
-    "startingTps": 100
+    "startTps": 100
   }
 }
 ```
@@ -126,7 +126,7 @@ The linear rate controller can be used in both duration-based and transaction nu
 The linear rate controller can be specified by setting the rate controller `type` to the `linear-rate` string.
 
 Controller options include:
-- `startingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
+- `startTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
 - `finishingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the end of the round
 
 The following example specifies a rate controller that gradually changes the transaction load from 25 TPS to 75 TPS during the benchmark round.
@@ -135,7 +135,7 @@ The following example specifies a rate controller that gradually changes the tra
 {
   "type": "linear-rate",
   "opts": {
-    "startingTps": 25,
+    "startTps": 25,
     "finishingTps": 75
     }
 }

diff --git a/docs/vNext/Rate_Controllers.md b/docs/vNext/Rate_Controllers.md
@@ -69,7 +69,7 @@ The fixed load rate controller is a controller for driving the tests at a target
 The fixed-load controller can be specified by setting the rate controller `type` to the `fixed-load` string.
 
 Controller options include:
-- `startingTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
+- `startTps`: the initial rate at which transactions are cumulatively sent to the SUT by all workers
 - `transactionLoad`: the number of transactions being processed by the SUT that is to be maintained
 
 The fixed load controller, aiming to maintain a SUT transaction load of 5, with a starting TPS of 100, is specified through the following controller option:
@@ -79,7 +79,7 @@ The fixed load controller, aiming to maintain a SUT transaction load of 5, with
   "type": "fixed-load",
   "opts": {
     "transactionLoad": 5,
-    "startingTps": 100
+    "startTps": 100
   }
 }
 ```
@@ -126,7 +126,7 @@ The linear rate controller can be used in both duration-based and transaction nu
 The linear rate controller can be specified by setting the rate controller `type` to the `linear-rate` string.
 
 Controller options include:
-- `startingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
+- `startTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the start of the round
 - `finishingTps`: the rate at which transactions are cumulatively sent to the SUT by all workers at the end of the round
 
 The following example specifies a rate controller that gradually changes the transaction load from 25 TPS to 75 TPS during the benchmark round.
@@ -135,7 +135,7 @@ The following example specifies a rate controller that gradually changes the tra
 {
   "type": "linear-rate",
   "opts": {
-    "startingTps": 25,
+    "startTps": 25,
     "finishingTps": 75
     }
 }