Summary
The workload manager is in charge of populating the database and spawning the different threads defined by the test configuration file for each database operation.

Without the workload manager (i.e when disabled), a test in a cppsuite probably does not make much sense.

We should probably not let the user disable it but rather have it always on by default. Furthermore, the workload manager being a component does not make much sense either. Whatever is in the run function of the workload manager could fit inside the run function of the test class. Ultimately, the workload manager may disappear.

Motivation

We wanted to define a component as a class that has a load, a run and a finish phase. The run phase would periodically perform a set of actions during the duration of the test. However, the workload manager does not fit in this category, hence we may want to think again if the workload manager is a component and if having a separate class is actually useful.

Acceptance Criteria (Definition of Done)

Decide whether the workload manager should remain a component and if its code would fit inside the test class.

• Documentation update
  Check the documentation written as part of WT-9109 and WT-9111