Pre-tests

Note

Beginning with version 5.3, Preconditioning Workloads phased out pre-tests across a number of releases. While existing pre-tests remain functional without changes, it is recommended that you use preconditioning workloads if they are available. Preconditioning workloads are available for FC and iSCSI. See Preconditioning for information regarding preconditioning workloads.

Next, define how you want the Pre-tests to run. Again, the concept of a Pre-test is to precondition the LUNs (for Block) and populate folders and files (for file). Pre-test is not mandatory if you have already preconditioned your LUN or populated the folders and files separately. Pre-test is recommended if you have not preconditioned your LUN or populated the folders and files.

2019-11-15_10-21-44.png
  • Run pre-tests as configured in Workloads. Use this option if you want some of your workloads to run a Pre-test but not others. In this case, the CW will honor each Workload’s Pre-test setting.

  • Run all pre-tests before Composite Workload. Use this option if you want to force the Pre-test to run for all workloads once prior to running the CW itself. In this case, the CW will not honor each Workload’s Pre-test setting, but instead force the Pre-test to run once for all Workloads.

  • Do not run pre-tests. Use this option if you do not want any Pre-test to run at all, and start running the CW itself.

  • Run pre-tests only. Use this option if you do not want to run the CW itself, but only the Pre-tests instead.