You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the e2e benchmarking tests, the test scenario is defined by a core set of parameters that influence the performance evaluation of the experiments. These parameters vary in nature; some are configuration settings, some are consensus/p2p parameters, and others define the network topology, etc. Consolidating these parameters in a single struct and ensuring that each testnet is associated with one and use that when setting up nodes, configurations, and parameters will simplify the process for test developers. This also facilitates the comparison of different test scenarios.
This issue aims to perform the necessary refactoring to achieve this.
The text was updated successfully, but these errors were encountered:
…es (#3391)
The first PR towards #3363Closes#3457
There will be an additional follow-up PR to further refactor the
`E2EThroughput`.
The `E2EThroughput` has been successfully tested (with the changes in
this PR) and is functioning properly.
You may run:
```
go run ./test/e2e/benchmark -v
```
In the e2e benchmarking tests, the test scenario is defined by a core set of parameters that influence the performance evaluation of the experiments. These parameters vary in nature; some are configuration settings, some are consensus/p2p parameters, and others define the network topology, etc. Consolidating these parameters in a single struct and ensuring that each testnet is associated with one and use that when setting up nodes, configurations, and parameters will simplify the process for test developers. This also facilitates the comparison of different test scenarios.
This issue aims to perform the necessary refactoring to achieve this.
The text was updated successfully, but these errors were encountered: